BBS in a Box 12/BBS in a box XII-2.iso/Files II/MacTechNotes/MacTN files by name

Text File | 1994-06-23 | 253.1 KB | 4,915 lines | [TEXT/R*ch]

 Name  =  10+ Commandments.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:10+ Commandments.sit
 Size: 17K         Date: 6/22/93         Version:
 Description:
 10+ Commandments - The world of Macintosh is changing rapidly. With a
plethora of new Macintosh CPUs and the prospect of even stranger, non-68K
CPUs on the horizon, how’s a programmer supposed to keep up? Maybe it’s
time to review some basic tenets of Macintosh programming and point out
some future pitfalls. Not only is it important that Apple evolve new
hardware; Apple must evolve the operating system as well. The issues
discussed here affect the ability of Apple to transform the Macintosh
Operating System into a modern operating system. As you write new code, or
review old code, be aware of these issues.

 Name  =  32-Bit QuickDraw V1.2.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:32-Bit QuickDraw V1.2.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 32-Bit QuickDraw V1.2 - This Technical Note describes the changes and
enhancements to 32-Bit QuickDraw from version 1.0 (as shipped on the
original Color Disk) to version 1.2, which ships with System Software 6.0.5
and later.  This Note assumes familiarity with Inside Macintosh, Volume V,
Color QuickDraw, and 32-Bit QuickDraw release notes.

 Name  =  +5 Volt Trickle.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:+5 Volt Trickle.sit
 Size:  6K         Date: 4/12/93         Version:
 Description:
 +5 Volt Trickle - One of the features of the new NuBus90 spec is the
availability of +5 trickle charge. There are some things that you will need
to know about this feature before you design any NuBus card. This Tech Note
will provide these things. NuBus90 +5 trickle feature, +5 trickle feature
on Macintosh, Possible problems with +5 trickle.

 Name  =  A/ROSE Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:A/ROSE Q&As.sit
 Size: 16K         Date:10/29/92         Version:
 Description:
 A/ROSE Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  A/UX Compatibility Guide.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:A/UX Compatibility Guide.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 A/UX Compatibility Guide - This Technical Note describes details of the
A/UX 2.0 implementation of which developers should be aware, so that their
Macintosh applications also work properly under A/UX. Changes since April
1989. This Note formerly described A/UX 1.1 Toolbox Bugs, but has been
completely rewritten to cover A/UX 2.0 compatibility. Changes since June
1990. Changes due to A/UX 2.0.1, also added some new important issues.

 Name  =  A/UX Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:A/UX Q&As.sit
 Size: 26K         Date:10/29/92         Version:
 Description:
 A/UX Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  A/UX  System Calls.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:A/UX  System Calls.sit
 Size: 21K         Date:10/29/92         Version:
 Description:
 A/UX  System Calls - This Technical Note discusses how to make A/UX system
calls from applications developed in the Macintosh environment.  This is
useful to anyone porting an existing Macintosh driver or application to
work on A/UX as well. Changes since August 1990. Added information about
how to make use of fork() system calls under MultiFinder, as well as how
various A/UX system calls behave under the MultiFinder emulation mode.

 Name  =  A5 and Patching traps.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:A5 and Patching traps.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 A5 and Patching traps - Future software may allow desk accessories to have
their own globals by changing register A5 when the accessory is entered and
exited. This can cause problems for applications that patch traps without
following certain rules.

 Name  =  A5 in GrowZone Procs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:A5 in GrowZone Procs.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 A5 in GrowZone Procs - If you have a grow zone function, it may get called
when a system routine is trying to allocate memory. Because this can
happen, you can’t be guaranteed that register A5 will be correct. If your
grow zone function depends on A5, you should save register A5, load A5 from
the low-memory global CurrentA5 (a long word at $904), and restore the
caller’s A5 before you exit.

 Name  =  ADB Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:ADB Q&As.sit
 Size: 17K         Date:10/29/92         Version:
 Description:
 ADB Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  ADBReInit in sys 4.2 - Don'.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:ADBReInit in sys 4.2 - Don'.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 ADBReInit in sys 4.2 - Because of a bug (which causes auto-repeat) in the
ROM version of the Macintosh SE keyboard driver, a patch was placed in
System 4.1. If ADBReInit is called, the ROM version of the keyboard driver
will be reloaded, and the RAM version of the driver with the patches will
not be used. Therefore, it is recommended that ADBReInit not be called on
the Macintosh SE until the problem is fixed. (There is no need to call
ADBReInit.) This problem will not occur with the Macintosh II ROM version
of the keyboard driver.

 Name  =  ADB (Space Aliens).sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:ADB (Space Aliens).sit
 Size: 26K         Date: 2/28/94         Version:
 Description:
 ADB (Space Aliens) - ADB–The Untold Story - Space Aliens Ate My Mouse
Hardware. This Technical Note explains a number of esoteric and unknown
issues concerning the Apple Desktop Bus (ADB). It incorporates material
from the original version of this note, along with a large amount of new
information, and is intended to detail information concerning all levels of
the ADB, from the hardware to the application usage level. This note is
supplementary to the information in The Guide To Macintosh Family Hardware
and in the Apple Desktop Bus Specification. The information in the
specification is the most accurate source of data, and unless it is
specifically refuted, it should be treated as the authoritative source.

 Name  =  ADSP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:ADSP Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 ADSP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  AFE Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:AFE Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 AFE Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  AFP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AFP Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 AFP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  ARA GetPortGlobal.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:ARA GetPortGlobal.sit
 Size:  7K         Date:12/07/93         Version:
 Description:
 ARA GetPortGlobal - This Technical Note documents the Remote Access Manager
(RAM) GetUserPortGlobalsPtr call. In order to make the RAM Status call on a
machine that is setup to answer calls, you must first make the
GetUserPortGlobalsPtr call to retrieve a pointer to the globals for the
user port. The Apple Remote Access (ARA) 1.0 client software supports
dial-out and answering capabilities through a single port called the “user”
port (the modem or printer port on your Mac). This means that when you
setup your machine to answer calls, you can answer only one call at a time
on the user port. However, the underlying ARA architecture was designed so
that in the future multiple ports may be supported...

 Name  =  ASP & AFP.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:ASP & AFP.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 ASP & AFP - The descriptions of the AppleTalk Session Protocol and
AppleTalk Filing Protocol functions within the body of the AppleTalk
Manager chapter are incorrect and conflict with those in the Summary of the
AppleTalk Manager. This technical note resolves the discrepancy. The
descriptions of the AppleTalk Session Protocol and AppleTalk Filing
Protocol functions which are described on pages 534 through 548 of Inside
Macintosh Volume V conflict with the descriptions in the Summary of the
AppleTalk Manager section, pages 554 through 559.

 Name  =  ATP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:ATP Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 ATP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  AT Remote Access Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AT Remote Access Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 AT Remote Access Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  AWS95 PerformanceGuide.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:AWS95 PerformanceGuide.sit
 Size: 14K         Date:11/10/93         Version:
 Description:
 AWS95 Performance Guide - The purpose of this Technical Note is to prov
insight into the workings of certain aspects of the AWS 95 so that a person
can make educated decisions on what and how to best configure and size the
AWS 95 for better performance. Before getting into details about how to
tune the AWS 95, the first section will discuss what kind of performance to
expect from the AWS 95, as well as explain the benchmarks that were used at
Apple to measure performance. The sections of this document which deal with
the AppleShare Caches also apply for AppleShare 4.0 performance tuning.

 Name  =  AWS95 Q&A.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:AWS95 Q&A.sit
 Size: 13K         Date:11/10/93         Version:
 Description:
 AWS95 Q&A - This technote provides questions and answers pertaining to the
Apple Workgroup Server 95. Some on the included questions - What is the
relative positioning of the Apple Workgroup Servers and AppleShare family
of products? What is the positioning the AWS 95 and AppleShare Pro against
its competitors? What Server and Services products are available and
shipping? What are the configurations and prices for the AWS family? Why
isn't AppleShare Pro bundled with every AWS95 configuration? Why are some
customers having problems ordering AppleShare Pro? What third party
applications are available for the Workgroup Server 95? And many more
questions (with answers of course)!

 Name  =  AWS Buffer Cache Q & A.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:AWS Buffer Cache Q & A.sit
 Size:  5K         Date:11/10/93         Version:
 Description:
 AWS Buffer Cache Q & A - This technical note discusses the buffer cache
the Apple Workgroup Server 95, how it affects performance and how to tune
your buffer cache to maximize performance. Some of the questions - What is
Unix buffer cache and how is it related to performance? How can proper
cache sizing be achieved? What is the cache setting for the default
File/Print as well as database configuration? What A/UX cache settings will
optimize server performance?

 Name  =  About AWS Tech Notes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:About AWS Tech Notes.sit
 Size:  4K         Date:11/10/93         Version:
 Description:
 About AWS (Apple Workgroup Server) Tech Notes - Technical notes are a
‘living’ complement to product documentation, be it Inside Macintosh or
other documentation. This means that they are updated on a regular basis,
so as to be accurate and up to date. New Notes are added as required. This
technical note is an index of all technical notes related to the Apple
Workgroup Servers and related products. It also documents all changes to
the technical notes since the previous release. August 1993.

 Name  =  Absolute Pointing Device.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Absolute Pointing Device.sit
 Size: 14K         Date:10/30/92         Version:
 Description:
 This Technical Note specifies a memory data structure for use by absolute
pointing devices; it was developed for the Apple Desktop Bus (ADB) but
could also be used for devices using serial input. Generally, this data
structure is created and updated by the pointing device’s driver and read
by either an application or the system cursor rendering software.

 Name  =  Accessing Globals From MPW.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Accessing Globals From MPW.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 Accessing Globals From MPW - This technical note demonstrates how to access
MPW Pascal and MPW C globals from the MPW Assembler.

 Name  =  AddDrive DrvrInstall.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:AddDrive DrvrInstall.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 AddDrive DrvrInstall - AddDrive, DrvrInstall, and _DrvrRemove are used in
the sample SCSI driver in the SCSI Development Package, which is available
from APDA. This Technical Note documents the parameters for these calls.
Changes since March 1, 1988. Updated the DrvrInstall text to reflect the
use of register A0, which should contain a pointer to the driver when
called. Also added simple glue code for DrvrInstall and DrvrRemove since
none is available in the MPW interfaces.

 Name  =  Alias Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Alias Mgr Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Alias Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Appearance Of Text.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Appearance Of Text.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Appearance Of Text - This technical note describes why text doesn’t always
look the way you expect depending on the environment you are in.

 Name  =  Apple Event Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Interapplication Comm.:Apple Event Mgr Q&As.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 Apple Event Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  AppleEventsSendtoSelf.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Interapplication Comm.:AppleEventsSendtoSelf.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 AppleEvents Send to Self - If an application suspends handling of an Apple
event which it sent to itself, the Apple Event Manager will return
errAETimeout as the result of the AESend call. The event was still sent
correctly, however, and the answer (if any) should appear later in the
reply descriptor. However, a problem in system software versions 7.0 and
7.0.1 prevents applications from getting the reply data.

 Name  =  AppleShare Foreground Apps.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleShare Foreground Apps.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 AppleShare Foreground Apps - This technical note outlines the requirements
and restrictions of an AppleShare foreground application. This information
pertains to AppleShare versions 1.1 and newer. An AppleShare server
requires a dedicated Macintosh. The server, however, is implemented as an
interrupt-driven application that runs in the system heap of the server
machine. This allows the running of a concurrent or foreground application
that will live in the application heap of the server machine. An example of
a foreground application is LaserShare, the LaserWriter spooler available
from Apple.

 Name  =  AppleShare Limits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleShare Limits.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 AppleShare Limits - This Technical Note describes some machine-dependent
limits of current versions of AppleShare and AppleShare servers. The
following chart lists some current AppleShare limits which are based upon
the chosen server platform and memory configuration.  The limits which
otherwise might be present on a workstation are still in effect and are not
affected by the workstation being logged into an AppleShare server. These
limits will change in the future.

 Name  =  AppleShareable Applications.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleShareable Applications.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 AppleShareable Applications - Normally, applications on an AppleShare
server volume cannot be executed by more than one user at a time. This
technical note explains why, and tells how you can enable your application
to be shared.

 Name  =  AppleShare and Old Finder.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleShare and Old Finder.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 AppleShare and Old Finder - A rumor has been spread that if you use a
pre-AppleShare Finder on a workstation to access AppleShare volumes, you
can bypass AppleShare’s “access privilege” mechanisms. This is not true.
Access controls are enforced by the server, not by the Finder. If you use
an older Finder, you are still prevented (by the server) from gaining
access to protected files and folders; however, you will not get the proper
user-interface feedback that you would if you were using the correct
Finder.

 Name  =  AppleTalk2.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleTalk2.sit
 Size: 63K         Date:10/29/92         Version:
 Description:
 AppleTalk2 - This Technical Note discusses the new features of AppleTalk
available for system software version 7.0 and AppleTalk version 57. The new
features include support for the Flagship Naming Service and the AppleTalk
Multiple Node Architecture. We present the Multiple Node Architecture and
discuss the new calls available to applications. We also discuss the impact
of the new architecture on AppleTalk Device files (ADEVs), and the changes
necessary to make them multinode compatible.

 Name  =  AppleTalk Interfaces.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleTalk Interfaces.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 AppleTalk Interfaces - What you need to do in order to use high-level
AppleTalk routines depends upon the interfaces you are using. Some
differences are outlined below.

 Name  =  AppleTalk Ov Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleTalk Ov Q&As.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 AppleTalk Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  AppleTalk Phase 2.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleTalk Phase 2.sit
 Size: 18K         Date:10/29/92         Version:
 Description:
 AppleTalk Phase 2 - This Technical Note discusses the new features and
calls available with AppleTalk Phase 2. Changes since August 1989.
Incorporated the ClosePrep and CancelClosePrep transitions and the new
control calls to the .MPP driver.

 Name  =  AppleTalk The Rest of.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleTalk The Rest of.sit
 Size: 68K         Date: 2/28/94         Version: 3/94
 Description:
 AppleTalk The Rest of the Story - This Technical Note discusses the
updates, and modifications to a number of facets of the lower levels of
AppleTalk Phase 2 since the release of Inside Macintosh Volume VI. Changes
as of February 1994 - Provide list of original AppleTalk Manager routines
which are NOT being ported to the PowerPC platform. Corrected the Multinode
Protocol glue to reflect that the AddNode call must be made as a
synchronous immediate Control call to the .MPP driver. Included information
on making the sample socket listener compatible with Virtual Memory. Added
note that the LAPAddATQ and LAPRmvATQ routines have been corrected in the
Interface.o library supplied with MPW v3.3. And much more!

 Name  =  AppleTalk Timers Explained.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:AppleTalk Timers Explained.sit
 Size: 10K         Date: 6/22/93         Version:
 Description:
 AppleTalk Timers Explained - This Technical Note explains how to
effectively use timers and retry mechanisms of the various AppleTalk
protocols to achieve maximum performance on an internet.

 Name  =  Apple’s Multidisk Installer.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Apple’s Multidisk Installer.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 Apple’s Multidisk Installer - This Technical Note documents Apple’s
Multidisk Installer, and it is in addition to separate Installer
documentation which provides the details of writing scripts.
Changes since September 1991, Revised information on the use of Installer
version 3.1 to version 3.2. Revised information on the use of ScriptCheck
version 3.2.1 with Installer version 3.2. Added Common Questions and
Answers relating to the use of the Installer.

 Name  =  Arbitr UseofAFPMisc.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Arbitr UseofAFPMisc.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Arbitr UseofAFPMisc - This Technical Note discusses a scheme for
arbitrating the use of the afpMiscUserCommand and afpMiscUserWrite
AppleTalk Filing Protocol (AFP) commands. Inside Macintosh Volume V lists
two AFP command codes that are reserved for developers. They are
afpMiscUserCommand (call number 191) and afpMiscUserWrite (call number
254). Several developers have asked that Apple arbitrate the use of those
two AFP calls. This Technical Note describes our recommended solution.

 Name  =  Author Index.sit
 Path =  AMUG CD2:Files II:MacTechNotes: Indexes:Author Index.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Author Index - This index lists each author and the Technical Notes they
are responsible for.

 Name  =  Available Volumes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Available Volumes.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Available Volumes - Standard File lets the user select one file from any
available volume; it is sometimes necessary for an application to find
which volumes are present. This technical note gives the proper method of
accomplishing this. There is a little-noticed feature of the low-level file
manager call PBHGetVInfo which allows specification of a “volume index” to
select the volume.

 Name  =  Avoid Using Network Events.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Avoid Using Network Events.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Avoid Using Network Events - Future System software enhancements will not
support network events. This note gives hints on weaning your application
from the use of network events.

 Name  =  Background-Only Apps.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Processes:Background-Only Apps.sit
 Size:  8K         Date:12/29/92         Version:
 Description:
 Background-Only Apps - Background-only applications (BOAs) are Macintosh
applications that run only in the background under MultiFinder and under
System 7. BOAs are the preferred alternative to INITs, drivers, and
stand-alone code for most startup-time and background “daemon” services.
This note discusses various issues that affect development of BOAs, as well
as useful implementation strategies for BOAs.

 Name  =  Basic QuickDraw Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Basic QuickDraw Q&As.sit
 Size: 29K         Date:10/29/92         Version:
 Description:
 Basic QuickDraw Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  BitMapToRegion.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:BitMapToRegion.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 BitMapToRegion - This Technical Note discusses the routine BitMapToRegion,
which converts a bitmap to a region, and is available in the 32-Bit
QuickDraw INIT and from Apple Software Licensing. Changes since October
1989. Added trap definitions for developers using the 32-Bit QuickDraw
version of this routine without the correct MPW include file.

 Name  =  Blessed Folder.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Blessed Folder.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Blessed Folder - This Technical Note describes how to determine which
folder on an HFS volume is the blessed folder, that is, the folder that
contains both the System file and the Finder. Changes since January 1986,
The information about how to find the "Blessed Folder" has been deleted
from this technical note. The FindFolder function can now be used to find
the "Blessed Folder" and is documented in Inside Macintosh Volume VI, pages
9-42 to 9-44. This note now includes information about how to bless a
folder to the new system folder.

 Name  =  Boot Blocks.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Boot Blocks.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Boot Blocks - There are two undocumented features of the Boot Blocks. This
note will describe how they currently work. Warning - The format and
functionality of the Boot Blocks will change in the future; dependence on
this information may cause your program to fail on future hardware or with
future System software.

 Name  =  Boot Problems.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Boot Problems.sit
 Size: 18K         Date:10/29/92         Version:
 Description:
 Boot Problems - The death of a hard disk with megabytes worth of data can
be exceedingly traumatic. This technical note will describe techniques for
recovering a hard disk and the data that is on it. The discussion will also
include some tips on how to avoid problems.

 Name  =  Borrowed AFP Sessions.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Borrowed AFP Sessions.sit
 Size: 11K         Date:10/29/92         Version:
 Description:
 Borrowed AFP Sessions - This Technical Note shows how to borrow the session
reference number of an AFP volume mounted by the Macintosh File System. It
also shows how to retrieve other information from the file system for a
mounted AFP volume.

 Name  =  Break/CTS Serial Driver Eve.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Break/CTS Serial Driver Eve.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Break/CTS Serial Driver Eve - This technical note documents the event
record information that gets passed when the serial driver posts an event
for a break/CTS status change. The serial driver can be programmed to post
a device driver event upon encountering a break status change or CTS change
(via the SerHShake call). The structure of device driver events is
driver-specific. This technical note documents the event record information
that gets passed when the serial driver posts a device driver event for a
break/CTS status change.

 Name  =  Bundles.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Bundles.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Bundles - A bundle is a collection of resources. Bundles can be used for a
number of different purposes, and are currently used by the Finder ito tie
an icon to a file type, allowing your application or data file to have its
own icon.

 Name  =  Bus Error Handlers.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Bus Error Handlers.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 Bus Error Handlers - This Technical Note discusses bus errors and how
applications and drivers should deal with them. Changes since February
1991, Discussion of why declaration ROMs are necessary in NuBus™ design.
This discussion is important for those who are considering using a
workaround instead of declaration ROMs. Also added are some hints that you
should be aware of if you are planning to write a bus error handler for the
’040.

 Name  =  Byte Smearing.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Byte Smearing.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Byte Smearing - This Technical Note discusses a feature of the current
Macintosh hardware which will not be supported in the future.  Macintosh
hardware developers and driver writers should be aware of this limitation
as it affects current and future products.

 Name  =  C++ Pitfalls.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:C++ Pitfalls.sit
 Size: 22K         Date:10/29/92         Version:
 Description:
 C++ Pitfalls - This Technical Note covers most of the common and serious
subtle problems that a MPW C++ user might encounter. For more information
consult the current C++ literature. This Note will be updated periodically
to reflect changes in the language and the compiler. Always read the
release notes included with the MPW C++ to find out the latest status for
known bugs and restrictions.

 Name  =  CDEF Params and Bugs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:CDEF Params and Bugs.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 CDEF Params and Bugs - This Technical Note describes known bugs in the
Control Manager which affect control definition functions ('CDEF'
resources). Changes since August 1988. Updated to reflect known bugs in the
posCntl and thumbCntl messages and the Control Manager _TrackControl call.

 Name  =  CD-ROM Driver Calls.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:CD-ROM Driver Calls.sit
 Size: 26K         Date: 6/22/93         Version:
 Description:
 CD-ROM Driver Calls - This Technical Note discusses the public interface to
the Apple CD-ROM driver, which currently supports the AppleCD SC, AppleCD
SC Plus/AppleCD 150, and the AppleCD 300. This information supercedes the
"Macintosh CD-ROM Device Driver" chapter of AppleCD SC Developer's guide
available through APDA. If you're writing special purpose application
software that needs to access the audio or data portions of a CD-ROM
directly, this note will be of interest to you.

 Name  =  CD-ROM Notes (Most Excellen.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:CD-ROM Notes (Most Excellen.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 CD-ROM Notes - This Technical Note discusses issues concerning the use of
the AppleCD SC drive, the Apple CD-ROM device driver, and the Foreign File
Access software extension.

 Name  =  CD-ROM Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:CD-ROM Q&As.sit
 Size: 11K         Date:10/29/92         Version:
 Description:
 CD-ROM Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  CD Remote DB Format.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:CD Remote DB Format.sit
 Size:  6K         Date: 5/30/94         Version: 2/94
 Description:
 CD Remote DB Format - February 1994. This Technical Note describes the
format of the “CD Remote Programs” database, as used in the “CD Remote”
desk accessory, the Hypercard CD Audio XCMDs, etc. Topics include - IndX
Resource Format, ProG Resource Format and STR# Resource. The file "CD
Remote Programs" is used by the CD Remote desk accessory, AppleCD Audio
Player, and other applications to retain information about an audio CD.
This file contains some master data in an ‘IndX’ resource. For each CD that
has been entered into the database, a resource of type ‘ProG’ and a
resource of type ‘STR#’ are kept.

 Name  =  CMOS On LC PDS.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:CMOS On LC PDS.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 CMOS On LC PDS - This Technical Note provides PDS card developers with some
important information about making PDS cards for the Macintosh LC. Due to
the way the Macintosh LC was designed, Apple strongly recommends that all
PDS cards be developed with CMOS parts.

 Name  =  Cache As Cache Can.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Cache As Cache Can.sit
 Size: 16K         Date:10/29/92         Version:
 Description:
 Cache As Cache Can - This Technical Note documents cache behavior,
manipulation of processor caches, and manipulation of external caches on
Macintosh models that incorporate these features. It also describes how
system software uses a memory management unit (when available) to implement
special caching options. Changes since October 1991. Described use of
AppleTalk Transition Queue event, ATTransSpeedChange, when altering the
68040 cache state on the fly. This call must be issued so that LocalTalk
can reevaluate its timers. Otherwise LocalTalk becomes disabled.

 Name  =  Caching.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Caching.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Caching - This technical note describes disk and File System caching on the
Macintosh, with particular emphasis on the high-level File System cache. Of
the three caches used for file I/O, this is the one which could have the
most impact on your program.

 Name  =  Calling SetResLoad.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Calling SetResLoad.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Calling SetResLoad - Calling SetResLoad(FALSE) can be useful if you need to
get a handle to a resource, without causing the resource to be loaded from
disk if it isn’t already in memory. SetResLoad changes the value of the
low-memory global ResLoad (at location $A5E).

 Name  =  Category Index.sit
 Path =  AMUG CD2:Files II:MacTechNotes: Indexes:Category Index.sit
 Size: 40K         Date:10/29/92         Version:
 Description:
 Category Index - This index lists each Technical Note by Cataogry, and
gives a brief description of of it's contents.

 Name  =  ChangedResource.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:ChangedResource.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 ChangedResource - The toolbox trap ChangedResource is used to inform the
Resource Manager that the contents of a resource have changed and should be
written to disk. The actual write occurs on the next call to WriteResource
(for the specific resource) or UpdateResFile (for the resource file
containing the specified resource). When called, ChangedResource reserves
enough disk space to contain the changed resource. A little-known “feature”
of ChangedResource is that it reserves disk space every time it is called.

 Name  =  Chooser Enhancements
.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Chooser Enhancements
.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 Chooser Enhancements - Beginning with version 3.2, the Chooser has been
enhanced to provide support for additional controls.

 Name  =  'ckid' Resource Format.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:'ckid' Resource Format.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 'ckid' Resource Format - This Technical Note describes the 'ckid' resource
format used by MPW’s Projector.  If you are writing an editor or
development system, you may wish to allow or disallow file modification
based on the information in the resource.

 Name  =  Clearing Completion.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Clearing Completion.sit
 Size:  4K         Date: 6/22/93         Version:
 Description:
 Clearing Completion - When making synchronous calls to the File Manager, it
is not necessary to clear ioCompletion field of the parameter block, since
that is done for you. Some earlier technotes explicitly cleared
ioCompletion, with the knowledge that this was unnecessary, to try to
encourage developers to fill in all fields of parameter blocks as indicated
in Inside Macintosh.

 Name  =  Clickless Sound.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Clickless Sound.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Clickless Sound - This Technical Note formerly described how to use the
Sound Driver to produce continuous sound without clicking. Changes since
March 1988. The continuous sound technique is no longer recommended.

 Name  =  Collaborative CompQ&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Interapplication Comm.:Collaborative CompQ&As.sit
 Size:  7K         Date: 6/22/93         Version:
 Description:
 Collaborative Comp Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Color Cursor Cursing.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Color Cursor Cursing.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Color Cursor Cursing - Working with color cursors you create from scratch
can cause headaches. This Technical Note may help a bit. Changes since June
1989. Added a warning about purgeable 'clut' resources.

 Name  =  Color Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Color Mgr Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Color Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Color Monitor Connection.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Color Monitor Connection.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Color Monitor Connection - This Technical Note describes how to connect the
Macintosh II Video Card, Macintosh IIci built-in video, and Macintosh LC
video to third-party monitors. Changes since February 1990. Added pinout
description for the Macintosh LC external video connector and a Macintosh
LC to VGA monitor adapter cable.  Standardized signal names throughout
Note.

 Name  =  Color Printing.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Color Printing.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Color Printing - This discusses color printing in a Macintosh application.
Whereas the original eight-color model of QuickDraw was sufficient for
printing in color on the ImageWriter II, the introduction of Color
QuickDraw has created the need for more sophisticated printing methods.

 Name  =  Color QuickDraw Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Color QuickDraw Q&As.sit
 Size: 39K         Date:10/29/92         Version:
 Description:
 Color QuickDraw Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  ColorSync Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:ColorSync Q&As.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 ColorSync Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Color, Windows & 7.0.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Color, Windows & 7.0.sit
 Size: 21K         Date:10/29/92         Version:
 Description:
 Color, Windows & 7.0 - System software version 7.0 introduces a new look
for the Macintosh desktop. In order to implement those changes, 'wctb' and
'cctb' resources have changed in both form and use; it is now up to
developers to take the lead and help the new standard work. The task can be
divided into two main areas: in most cases all developers have to do is to
stick to the system resources in order to provide a homogeneous feel to the
user; developers in this group need only make sure the old 'wctb's are
disposed of and that all dialogs and windows are based on CGrafPorts.

 Name  =  Colorizing CopyBits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Colorizing CopyBits.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Colorizing CopyBits - Inside Macintosh Volume V states that the foreground
and background colors are applied to an image during a CopyBits or CopyMask
call. Accidental use of this feature can create bizarre coloring effects.
This note explains what happens, how to avoid problems, and how to use it.

 Name  =  Comm Toolbox Ov Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Communications:Comm Toolbox Ov Q&As.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 Comm Toolbox Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Command-Shift Keys.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:Command-Shift Keys.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Command-Shift Keys - In the standard system, there are two Command-Shift-
number key combinations that are automatically captured and processed by
GetNextEvent.

 Name  =  Compatability Guidelines.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Compatability Guidelines.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Compatability Guidelines - Apple has many enhancements planned for the
Macintosh family of computers. To help ensure your software’s compatibility
with these enhancements, check each item in this note to be sure that
you’re following the recommendations.

 Name  =  Compatibility Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Compatibility Q&As.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 Compatibility Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Compatibility Why and How.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Compatibility Why and How.sit
 Size: 29K         Date:10/29/92         Version:
 Description:
 Compatibility Why and How - While creating or revising any program for the
Macintosh, you should be aware of the most common reasons why programs fail
on various versions of the Macintosh. This note will detail some common
failure modes, why they occur, and how to avoid them.

 Name  =  Compleat TeachText.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Compleat TeachText.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 Compleat TeachText - This Technical Note explains how to use TeachText to
create release notes, complete with pictures, which every Macintosh owner
can read.  This Note assumes familiarity with ResEdit.

 Name  =  Component Manager 3.0.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:Component Manager 3.0.sit
 Size: 17K         Date: 5/03/94         Version: 3.0
 Description:
 Component Manager 3.0 - Written by -    Jim Reekes & Dave Radcliffe    March
1994. This note contains information regarding the version of the Component
Manager that shipped with QuickTime 1.6 and the changes necessary to
support native PowerPC components. Topics - QuickTime 1.6 and Component
Manager 3.0 , Native PowerPC components. The Component Manager in QuickTime
1.6.x and for the Power Macintosh (PowerPC) release has some new features.
It has added the ability to automatically resolve conflicts between
different versions of the same component. It will ensure that only the most
recent version of a given component is actually registered.

 Name  =  Component Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Component Mgr Q&As.sit
 Size:  7K         Date: 6/22/93         Version:
 Description:
 Component Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Composite SIMMs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Composite SIMMs.sit
 Size:  6K         Date: 8/26/93         Version:
 Description:
 Composite SIMMs - This Technical Note discusses composite SIMMs and why
they shouldn’t be used on Macintosh computers. A composite SIMM is defined
as a SIMM made up of banks of many smaller DRAM devices, with additional
bank-controlling circuitry and perhaps buffers for the address and control
signals. Composite SIMMs pose timing and electrical problems in some
Macintosh computers, particularly those optimized for maximum DRAM
performance, such as the Macintosh Centris 610, Macintosh Centris 650,
Macintosh Quadra 800, and the Macintosh Quadra 900 series.

 Name  =  Configuring Inodes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:Configuring Inodes.sit
 Size:  6K         Date:11/10/93         Version:
 Description:
 Configuring Inodes - This technical note documents methods for
tuning/creating a UNIX file system with lower overheads in terms of inode
allocation, which proves to be important in large size file systems by
reclaiming disk space. The newfs command makes a Berkeley 4.2 UNIX file
system (UFS) on the specified device file. The A/UX version of HD SC Setup
invokes newfs when creating a UFS. Each file on the system is represented
by an inode, which contains critical information about the file, including
ownership, permissions, size, etc. The newfs command allocates disk space
for inodes when the UFS is created. Find out more!

 Name  =  Connection Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Communications:Connection Mgr Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Connection Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Control Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Control Mgr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Control Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Control Panel Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Control Panel Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Control Panel Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Coop with Coprocessor.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Coop with Coprocessor.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Coop with Coprocessor - The use of the 68881 or 68882 coprocessor is
usually handled by the SANE package or by a development system’s libraries.
Some developers may wish to use the coprocessor during special
circumstances, such as at interrupt level or installing their own hardware
floating point exception handlers. In these two situations, there are
special requirements that must be met. These requirements will require
floating–point assembly code and are discussed in this Technical Note.

 Name  =  CopyBits & GC QuickDraw.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:CopyBits & GC QuickDraw.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 CopyBits & GC QuickDraw - This Technical Note discusses conditions that may
cause _CopyBits to slow down when QuickDraw acceleration is on via the
Apple 8•24 GC Display Card.

 Name  =  Correct PlatformChoice.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:Correct PlatformChoice.sit
 Size:  3K         Date:11/10/93         Version:
 Description:
 Correct Platform Choice - With the release of the Apple Workgroup Server 95
there has been confusion with respect to guiding customers towards
selecting the proper platform for their specific needs. In a number of
instances the database version of this product has been selected when what
the customer required was really the File/Print Server. ACIUS Inc. is
shipping their version of the 4th Dimension server. It will be important to
make sure that people who want to obtain this product combination
understand that the proper platform is the File/Print Server and not the
database server product.

 Name  =  CreateResFile & PMSP.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:CreateResFile & PMSP.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 CreateResFile & PMSP - CreateResFile checks to see if a resource file with
a given name exists, and if it does, returns a dupFNErr (–48) error.
Unfortunately, to do this check, CreateResFile uses a call that follows the
Poor Man’s Search Path (PMSP).

 Name  =  Creating In Drop Folders.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Creating In Drop Folders.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Creating In Drop Folders - This technical note outlines the steps an
application must take to create files inside AppleShare drop folders.
The AppleShare File Server allows the creation of drop folders. These are
folders for which the user has the Make Changes privilege (write access),
but not See Files (read access) or See Folders (search access).

 Name  =  Custom Menu Flashing Bug.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Custom Menu Flashing Bug.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Custom Menu Flashing Bug - Selected menu items in a custom 'MDEF' resource
do not flash correctly due to a bug in the Menu Manager.  This Technical
Note describes the problem and explains how to make your 'MDEF' flash
correctly.

 Name  =  Custom WDEF and wDraw.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Custom WDEF and wDraw.sit
 Size:  4K         Date: 6/22/93         Version:
 Description:
 Custom WDEF and wDraw - This Technical Note explains why custom window
definition functions may not respond to a wDraw message from the system (if
you follow the documentation in Inside Macintosh).

 Name  =  DAM Extensions.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:DAM Extensions.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 DAM Extensions - This Technical Note discusses coding data access
extensions that provide an interface between the Data Access Manager and
remote data sources. Each of the functions that a data access extension
must implement is described.

 Name  =  DB to File/DB server.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:DB to File/DB server.sit
 Size:  4K         Date:11/10/93         Version:
 Description:
 DB to File/DB server - This technical note discusses how to convert your
Apple Workgroup Server 95 Database Server running Oracle 7 to a combined
Apple Workgroup Server 95 Database/File/Print Server running Oracle 7 and
AppleShare Pro. The File/Print Server addition to a Apple Workgroup Server
95 Database Server requires many steps, which are fully explained in the
documentation.

 Name  =  DB to File server.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:DB to File server.sit
 Size:  5K         Date:11/10/93         Version:
 Description:
 DB to File server - This technical note discusses how to change your Apple
Workgroup Server 95 Database Server running Oracle 7 to a File/Print Server
running AppleShare Pro. Changing to a Apple Workgroup Server 95 File/Print
Server requires many steps to be taken, all of which are listed and fully
explained in the documentation.

 Name  =  DDP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:DDP Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 DDP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Data In Resource Fork.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Data In Resource Fork.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Data In Resource Fork - Don’t use the resource fork of a file for
non-resource data. Parts of the system (including the File Manager and the
Finder) assume that if this fork exists, it will contain valid Resource
Manager information. PBOpenRF was provided to allow copying of the resource
fork of a file in its entirety, without Resource Manager interpretation. Do
not use it to open “another data fork.”

 Name  =  Debugging Tips.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Debugging Tips.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Debugging Tips - This presents a few tips which may make your debugging
easier.

 Name  =  Debug with Purge.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Debug with Purge.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Debug with Purge  - If you are having problems finding bugs like handles
that aren’t locked down when they should be, or resources that aren’t there
when they’re supposed to be, there is a handy technique for forcing these
problems to the surface.

 Name  =  Deferred Task Traps.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Processes:Deferred Task Traps.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Deferred Task Traps - This Technical Note shows how to determine when the
Deferred Task Manager is available, points out a compatibility issue with
the Macintosh Plus, explains how and when deferred tasks are called, and
shows how to access the dtParm parameter from deferred tasks written in C
and Pascal.

 Name  =  Dependent Files.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:Dependent Files.sit
 Size: 10K         Date: 6/22/93         Version:
 Description:
 Dependent Files - This Technical Note describes how to identify and work
with dependent files, which are files that reference or are referenced by
other files. It also documents QuickTime's dependent file format.

 Name  =  DeskHook and INIT Evils.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:DeskHook and INIT Evils.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 DeskHook and INIT Evils - This Technical Note discusses INIT evils, the
foremost of which deals with clearing DeskHook and DragHook at INIT time.
Changes since August 1989. Added warning about clearing DragHook.

 Name  =  Desktop File Limits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Desktop File Limits.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Desktop File Limits - There is a limit to the number of applications/files
that the Finder can “see” on a single volume. This limitation is imposed by
the Desktop file. The Desktop file is a resource file that the Finder uses
to keep track of information about files and applications, including Finder
file comments (Get Info comments), and how these files and applications
relate to each other.

 Name  =  Desktop File Resources.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Desktop File Resources.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Desktop File Resources - This Technical Note describes the resources found
in the Desktop file.  You should not base anything critical on the format
of the Desktop file. System 7 already uses another scheme as did AppleShare
2.0 under System 6.0.x.

 Name  =  Desktop Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Desktop Mgr Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Desktop Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Device Driver Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Device Driver Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Device Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Device Independen Printing.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Device Independen Printing.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Device Independen Printing - The Printing Manager was designed to give
Macintosh applications a device- independent method of printing, but we
have provided device-dependent information, such as the contents of the
print record. Due to the large number of printer-type drivers becoming
available (even for non-printer devices) device independence is more
necessary than ever. What this means to you, as a developer, is that we
will no longer be providing (or supporting) information regarding the
internal structure of the print record.

 Name  =  Device Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Device Mgr Q&As.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 Device Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Device Mgt Ov Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Device Mgt Ov Q&As.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 Device Mgt Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Dialog Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Dialog Mgr Q&As.sit
 Size: 16K         Date:10/29/92         Version:
 Description:
 Dialog Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Dictionary Downloading.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Dictionary Downloading.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 Dictionary Downloading - This technical note discusses a method for
downloading PostScript dictionaries automatically using the LaserWriter
driver. It will also provide the format and use of the PREC(103) resource.
It will also describe some problems with the now obsolete PREC(201)
resource. If you are using PostScript dictionaries, or either of these
resources, you should definitely read this note.

 Name  =  Directory Handling Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Directory Handling Q&As.sit
 Size: 17K         Date:10/29/92         Version:
 Description:
 Directory Handling Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Disk Driver Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Disk Driver Q&As.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 Disk Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Displaying Large PICT Files.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Displaying Large PICT Files.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 Displaying Large PICT Files - Now that we have scanners and other
massive-picture producing types of applications, there is a need to address
the problem of how to display a PICT format object that is bigger than a
current PICT resource is allowed to be. Note that this technique applies
equally well to version 1 and version 2 (word-opcode) pictures as produced
by the Macintosh II.

 Name  =  Docking Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Docking Mgr Q&As.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 Docking Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Document Names.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Document Names.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Document Names - Our compatibility testing for LaserShare (Apple’s
LaserWriter spooler) has turned up a number of applications that do not
provide the Printing Manager with a document name; although this feature is
not required, it is nice for users that share printers.

 Name  =  Don’t Call ADBReInit in sys.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Don’t Call ADBReInit in sys.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Don’t Call ADBReInit in sys - Because of a bug (which causes auto-repeat)
in the ROM version of the Macintosh SE keyboard driver, a patch was placed
in System 4.1. If ADBReInit is called, the ROM version of the keyboard
driver will be reloaded, and the RAM version of the driver with the patches
will not be used. Therefore, it is recommended that ADBReInit not be called
on the Macintosh SE until the problem is fixed. (There is no need to call
ADBReInit.) This problem will not occur with the Macintosh II ROM version
of the keyboard driver.

 Name  =  Drawing Icons.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Drawing Icons.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Drawing Icons - Using resources of type ICON allows drawing of icons in
srcOr mode.  Using resources of type ICN# allows for more variety when
drawing icons.

 Name  =  Drawing Text in Narrow Graf.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Drawing Text in Narrow Graf.sit
 Size:  4K         Date: 6/22/93         Version:
 Description:
 Drawing Text in Narrow Graf - When you draw a character into a GrafPort,
your program will die with an address error if the width of the GrafPort is
smaller than the width of the character. If you check before drawing the
character to see if the GrafPort is wide enough, you can avoid this
unfortunate tragedy.

 Name  =  Drive Queue Elements.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Drive Queue Elements.sit
 Size:  7K         Date: 6/22/93         Version:
 Description:
 Drive Queue Elements - This note expands on Inside Macintosh’s definition
of the drive queue, which is given in the File Manager chapter.

 Name  =  Driver Education.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Driver Education.sit
 Size: 26K         Date: 6/22/93         Version:
 Description:
 Driver Education - This Technical Note describes in detail the operation of
the Device Manager and its interaction with device drivers. It provides the
background needed for correct operation of third-party device drivers and
also presents a method for finding an entry in the Unit Table for a driver.

 Name  =  Drivers & DAs in.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Drivers & DAs in.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 Drivers & DAs in - This Technical Note describes a few complications which
rear their rather ugly little heads when a desk accessory or driver needs
periodic time. It also presents a few solutions to work around these
problems and make life easier, at least periodically.

 Name  =  Edit File Format.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Edit File Format.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Edit File Format - This technical note describes the format of the files
created by Edit. It has been verified for versions 1.x and 2.0.

 Name  =  Edition Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Interapplication Comm.:Edition Mgr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Edition Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Error in FCBPBRec.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Error in FCBPBRec.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Error in FCBPBRec - The declaration of a FCBPBRec is wrong in Inside
Macintosh Volume IV  and early versions of MPW. This has been fixed in MPW
1.0 and newer. An error was made in the declaration of an FCBPBRec
parameter block that is used in PBGetFCBInfo calls. The field ioFCBIndx was
incorrectly listed as a LONGINT.

 Name  =  Errs Returned from GetNewDi.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Errs Returned from GetNewDi.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Errs Returned from GetNewDi - When calling GetNewDialog to retrieve a
dialog template from a previously opened resource file, how are error
conditions indicated to the caller? Unfortunately, they aren’t. The Dialog
Manager calls GetResource and assumes the returned value is good.

 Name  =  Ethernet Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Ethernet Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Ethernet Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Event Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Event Mgr Q&As.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 Event Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Every Picture [Comment] Tel.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Every Picture [Comment] Tel.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Every Picture [Comment] Tel - Application-specific picture comment conflict
and registration is addressed, along with Developer Technical Support’s
method for solving it.

 Name  =  Excellent CD Notes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Excellent CD Notes.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Excellent CD Notes - This Technical Note discusses issues concerning the
use of the AppleCD SC drive, the Apple CD-ROM device driver, and the
Foreign File Access software extension.

 Name  =  FPU Operations on Quadras.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:FPU Operations on Quadras.sit
 Size: 19K         Date:10/29/92         Version:
 Description:
 FPU Operations on Quadras - This Technical Note discusses floating-point
unit (FPU) instruction support on Macintosh Quadra platforms with special
emphasis given to compatibility and performance concerns. Changes since
June 1992. Added warning to check for an FPU before attempting to execute
FPU instructions.

 Name  =  Fear No SCSI.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Fear No SCSI.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 Fear No SCSI - This Technical Note discusses the answers to questions that
are often asked about SCSI and that are not discussed in Inside Macintosh
Volumes IV and V.

 Name  =  Feeder Fodder.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Feeder Fodder.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Feeder Fodder - This Technical Note discusses the new Feeder button
available in the 6.1, and 7.0 versions of the LaserWriter driver.  This
Feeder button mechanism allows developers to insert code into the
LaserWriter driver to support a sheet feeder connected to a LaserWriter.
This Note provides a description of the button, as well as information
required to implement one.

 Name  =  File Handling Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:File Handling Q&As.sit
 Size: 28K         Date:10/29/92         Version:
 Description:
 File Handling Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  File Mgt Overview Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:File Mgt Overview Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 File Mgt Overview Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  File Sharing .sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:File Sharing .sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 File Sharing - This Note describes modifications to the existing File
Manager routines, PBGetCatInfo, PBHGetDirAccess, PBHSetDirAccess,
PBHSetFLock and PBHRstFLock, when used on volumes prepared by Macintosh
System 7 File Sharing. There are several differences between System 7 File
Sharing and AppleShare 2.0.1. This Note describes what those differences
mean when calling PBGetCatInfo, PBHGetDirAccess, PBHSetDirAccess,
PBHSetFLock and PBHRstFLock on local volumes that return bHasPersonal
AccessPrivileges to PBHGetVolParms.

 Name  =  File to DB server.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:File to DB server.sit
 Size:  5K         Date:11/10/93         Version:
 Description:
 File to DB server - This technical note discusses how to change your Apple
Workgroup Server 95 (AWS 95) File/Print Server running AppleShare Pro to be
a Apple Workgroup Server 95 Database Server running Oracle 7. Changing to
an Apple Workgroup Server 95 Database Server requires many steps to be
taken, all of which are described in the tech note.

 Name  =  File to File/DB Server.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:File to File/DB Server.sit
 Size:  5K         Date:11/10/93         Version:
 Description:
 File to File/DB Server - This technical note discusses how to convert your
Apple Workgroup Server 95 (AWS95) File/Print Server running AppleShare Pro
to a combined Apple Workgroup Server 95 File/Print Server/Database Server
running AppleShare Pro and Oracle 7. The Database Server addition to an
Apple Workgroup Server 95 File/Print Server requires many steps to be
taken, all of which are explained in this tech note.

 Name  =  FindDItem.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:FindDItem.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 FindDItem - FindDItem is a potentially useful call which returns the number
of a dialog item given a point in local coordinates and a dialog handle. It
returns an item number of –1 if no item’s rectangle overlaps the point.
This is all well and good, except you don’t get back quite what you would
expect.

 Name  =  Finder Flags.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Finder Flags.sit
 Size:  6K         Date: 2/28/94         Version: 11/93
 Description:
 Finder Flags - The Finder keeps and uses a series of file information flags
for each file. These flags are located in the fdFlags field (a word at
offset $28 into an HParamBlockRec) of the ioFlFndrInfo record of a
parameter block. For directories, the flags are located in the frFlags
field of the ioDrUsrWds record of a parameter block (also offset $28).
They may change with newer versions of the Finder. Finder 7.1.1 assigns the
following meanings to the flags (see the actual file). Changes since March
1988 - This version updates the meanings of several of the bits which
changed in System 7 and System 7 Pro.

 Name  =  Finder Notes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Finder Notes.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Finder Notes - The Finder has undergone a couple of changes you should keep
in mind when creating the “bundle” information for your application.

 Name  =  Finder Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Finder Q&As.sit
 Size: 19K         Date:10/29/92         Version:
 Description:
 Finder Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Finders and Drives.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Finders and Drives.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Finders and Drives - This technical note describes the differences in the
way the 1.1g, 4.1, 5.0 and newer Finders communicate with foreign
(non-Sony) disk drives.

 Name  =  Finding Drivers in Unit.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Finding Drivers in Unit.sit
 Size:  6K         Date: 5/30/94         Version:
 Description:
 Finding Drivers in Unit - DV 6 - Finding Drivers in the Unit Table
Devices    M.DV.FindingDrivers. Revised by -    Rich Kubota    September 1993
Written by -    Rick Blair    February 1986. This note will explain how code can
be written to determine the reference number of a previously installed
driver when only the name is known. Changes since February 1986 - Corrected
the C sample code specifically for "do…while" loop to continue while the
driverName did not match that of the name of the driver for a unit entry.
You should already be familiar with The Device Manager chapter of Inside
Macintosh before reading this technical note.

 Name  =  Finding Drivers in.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Finding Drivers in.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Finding Drivers - This note will explain how code can be written to
determine the reference number of a previously installed driver when only
the name is known. Changes since 2/86, Since the driver can be purged and
the DCE still be allocated, the code now tests for dCtlDriver being NIL as
well.

 Name  =  Fixed CLUT Devices.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Fixed CLUT Devices.sit
 Size:  7K         Date: 6/22/93         Version:
 Description:
 Fixed CLUT Devices - Applications that need a given set of colors to look
good or make use of color table animation can obtain undesired results in
PowerBook 160, PowerBook 180, and PowerBook Duo Macintosh models. The
reason for this is that these models sport Fixed Color Devices associated
with the flat screen display. This Tech Note describes what a Fixed CLUT
device is and presents some solutions to the challenges presented by this
display type.

 Name  =  Floppy Disk Int Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Floppy Disk Int Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Floppy Disk Int Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Fond of FONDs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Fond of FONDs.sit
 Size: 25K         Date:10/29/92         Version:
 Description:
 Fond of FONDs - This Technical Note takes the place of Tech Note #26,
“Character vs. String Operations in QuickDraw” by Bryan Stearns (March
1988), which pointed out the possible differences between the results of a
StringWidth call and successive calls to CharWidth. This Note updates and
brings into a broader context the issues related to text measuring. It also
provides additional documentation on font family resources ('FOND's), and
addresses various other frequently asked questions related to the Font
Manager.

 Name  =  Font Family Numbers.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Fonts:Font Family Numbers.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Font Family Numbers - This Technical Note discusses the range of numbers
available for identifying font families, how they are allocated among
script systems, and what numbers should be used for fonts that were
designed to be used as a tool in an application. Changes since August 1990.
Apple Computer no longer registers font family ID numbers; this note has
been altered to reflect the change in policy. Also, the relationship of
outline fonts to font families is discussed briefly.

 Name  =  Font File Icons.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Fonts:Font File Icons.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Font File Icons - This Technical Note discusses why you should not link
directly from your font files to the font icons provided by LaserWriter
driver 5.2 and later. Changes since December 1988. Added some useful tips
and described the method required to bundle an icon to your font file.

 Name  =  Font Height Tables.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Font Height Tables.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Font Height Tables - This technical note describes how the Font Manager
(except in 64K ROMs) calculates height tables for fonts and how you can
force recalculation.

 Name  =  Font Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Font Mgr Q&As.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 Font Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Font Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Font Mgr Q&As.sit
 Size: 14K         Date:12/07/93         Version:
 Description:
 Font Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals. New Q&As
in this Technical Note - RealFont causes system heap to grow and Embedding
fonts in applications.

 Name  =  Font Names.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Fonts:Font Names.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Font Names - This note recommends the use of font names rather than font
numbers. The Font Manager chapter of Inside Macintosh Volume IV claims that
font family numbers 0 through 127 are reserved for use by Apple, and
numbers 128 through 255 are assigned by Apple for fonts created by software
developers. This is no longer true. Developer Technical Support does not
assign font family numbers. You should only use font numbers to reference
the system font (font 0) and application default font (font 1). All other
fonts should be identified by name. The Font/DA Mover will renumber a font
when moving it into a file containing a conflicting font family.

 Name  =  Fonts and the Script Mgr.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Fonts and the Script Mgr.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Fonts and the Script Mgr - This Technical Note describes how the Script
Manager uses the font family ID to determine a script code.

 Name  =  Forcing Floppy Size.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Forcing Floppy Size.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Forcing Floppy Size - This document explains how to initialize a disk as
either single- or double- sided. It only applies to 800K drives, of course.
You can call the disk driver to initialize a disk and determine
programmatically whether it should be initialized as single- (MFS) or
double- (HFS) sided. All you have to do is call the .Sony driver directly
to do the formatting then the Disk Initialization Package to write the
directory information.

 Name  =  Fun with PrJobMerge (#2).sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Fun with PrJobMerge (#2).sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Fun with PrJobMerge (#2) - This Technical Note discusses some interesting
behavior you’ll encounter while using PrJobMerge with the 7.0 and 7.1
versions of the LaserWriter driver. Changes since March 1992. Corrected the
Vulcan-like “THPring” typo to correctly read “THPrint,” and changed a
comment in the code to mean what I originally meant.

 Name  =  GDevice Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:GDevice Mgr Q&As.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 GDevice Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Gestalt & Sysenvirons.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Gestalt & Sysenvirons.sit
 Size: 12K         Date: 6/22/93         Version:
 Description:
 Gestalt & Sysenvirons - This Technical Note discusses the latest changes
and improvements to the _Gestalt and _SysEnvirons calls.

 Name  =  Gestalt Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:Gestalt Mgr Q&As.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Gestalt Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  GetNextEvent & Blinking App.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:GetNextEvent & Blinking App.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 GetNextEvent & Blinking App - Wherein arcane mysteries are unraveled so you
can make the Alarm Clock (or a similar desk accessory) blink the Apple menu
at the appointed second. Also, why GetNextEvent is a good thing.

 Name  =  Getting a Full Pathname.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Getting a Full Pathname.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Getting a Full Pathname - This Technical Note describes how to generate a
full pathname, given either a Working Directory ID or a real vRefNum and a
DirID. By using the techniques shown in this Note, you can find the full
pathname from information such as that returned by Standard File. Changes
since June 89. Added a note on how to check for A/UX. Fixed bug in C
version:  BlockMove() parameters were reversed in pStrcpy(); added range
checking to pStrCat(); changed references from “longint” to “long”.  Fixed
bug in Pascal and C versions. Changed fsRtDir to fsRtdirID and made
references to gHaveAUX consistent.

 Name  =  Getting thru CUSToms.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Getting thru CUSToms.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 Getting thru CUSToms - This technical note provides a way for developers to
allow sophisticated users to add code to an off-the-shelf application.
Using this scheme, the user can easily install the code module; the
application has to know how to call it and, optionally, be able to respond
to a set of predefined calls from the custom package.

 Name  =  Glue Code.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Glue Code.sit
 Size: 12K         Date: 6/22/93         Version:
 Description:
 Glue Code - This Technical Note describes glue code, explains how it
quietly improves your complicated life, and shows you how to write your own
when necessary.

 Name  =  HFS Comaptibility.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:HFS Comaptibility.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 HFS Comaptibility - This technical note tells you how to make sure that
your applications run under the Hierarchical File System (HFS). The
Hierarchical File System (HFS) provides fast, efficient management of
larger volumes than the original Macintosh File System (MFS). Since HFS is
hierarchical, HFS folders have a meaning different from MFS folders. In
MFS, a folder has only graphical significance—it is only used by the Finder
as a means of visually grouping files. The MFS directory structure is
actually flat (all files are at the ‘root’ level). Under HFS, a folder is a
directory that can contain files and other directories.

 Name  =  HFS Elucidations.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:HFS Elucidations.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 HFS Elucidations - This technical note will describe a few problems that
can occur while using HFS. It will also describe ways to avoid these
problems.

 Name  =  HFS Ruminations.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:HFS Ruminations.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 HFS Ruminations - This technical note contains some thoughts concerning
HFS.

 Name  =  HFS Tidbits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:HFS Tidbits.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 HFS Tidbits - This Technical Note describes two poorly documented features
of the File Manager.

 Name  =  Handles vs. Pointers.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:Handles vs. Pointers.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Handles vs. Pointers - A handle is a handle and a pointer is a pointer.
Applications should avoid embedding non-relocatable objects (that the
system assumes will never move) in handles. In order to avoid
fragmentation, some applications embed pointers (non-relocatable memory
manager objects) in handles, so that the handles can be moved around as
needed. This can cause several problems, especially with the Macintosh II,
and should be avoided.

 Name  =  Hard Disk Hacking.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Hard Disk Hacking.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Hard Disk Hacking - For those of a technical bent with some extra time, you
can build your own hard disk system from a cheap SCSI drive and a driver
that you write. This is not a project for those short on time, so beware.

 Name  =  Hard Disk Medic.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Hard Disk Medic.sit
 Size: 18K         Date: 6/22/93         Version:
 Description:
 Hard Disk Medic - The death of a hard disk with megabytes worth of data can
be exceedingly traumatic. This technical note will describe techniques for
recovering a hard disk and the data that is on it. The discussion will also
include some tips on how to avoid problems.

 Name  =  Help Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Help Mgr Q&As.sit
 Size: 17K         Date:10/29/92         Version:
 Description:
 Help Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  High-Level AppleTalk Routin.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:High-Level AppleTalk Routin.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 High-Level AppleTalk Routin - What you need to do in order to use
high-level AppleTalk routines depends upon the interfaces you are using.
Some differences are outlined below.

 Name  =  High Level Control & Stat.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:High Level Control & Stat.sit
 Size:  7K         Date: 6/22/93         Version:
 Description:
 High Level Control & Stat - This Technical Note discusses situations under
which high-level Status calls do not work correctly and PBStatus calls
should be made instead. Changes since February 1990-Information has been
added describing similar problems with high-level Control calls.

 Name  =  HyperCard and You.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:HyperCard and You.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 HyperCard and You - This Technical Note describes some HyperCard anomalies
with which developers should be familiar when developing stackware, and it
documents differences between HyperCard versions where appropriate.
Changes since November 1987. Updated material with regard to HyperCard 2.0
and condensing or obsoleting information on bugs which have been addressed.

 Name  =  IOP Diffs Under A/UX.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:IOP Diffs Under A/UX.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 IOP Diffs Under A/UX - This Technical Note discusses use of the Macintosh
IIfx IOP-based serial driver under A/UX, especially under certain error
conditions which cause it to perform differently than documented in
termio(7).  (The SCC driver, used on non-IOP machines, conforms to
termio(7) in all cases.)  References to “the driver” herein refer to the
IOP-based serial driver, seriop.c.

 Name  =  ISO 9660 CD ROM Format.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:ISO 9660 CD ROM Format.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 ISO 9660 CD ROM Format - What’s Wrong with my High Sierra Disc? Generally,
if a Macintosh has problems with a High Sierra disc, it’s because the disc
in question  doesn’t really conform to the High Sierra specification.

 Name  =  ISO 9660 Extensions.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:ISO 9660 Extensions.sit
 Size: 14K         Date: 5/30/94         Version: 2/94
 Description:
 ISO 9660 Extensions - FL 36 - Apple Extensions to ISO 9660 Files.
M.FL.ISO9660Extensions. Revised by -    Brian Bechtel    February 1994. Written
by -    Bryan Atsatt & Brian Bechtel    July 1989. This Technical Note describes
extensions Apple has defined to ISO 9660 in order to better support
Macintosh file interchange. ISO 9660 is an international standard for
formatting CD-ROM discs. This tech note is only important if you are a
publisher of authoring tools for ISO 9660 discs, or are interested in
details of how the Macintosh supports ISO 9660. Topics include - ISO 9660
compared to HFS, The directory record SystemUse field, The extension to ISO
9660, ISO 9660 Associated files and Version numbers in ISO 9660.

 Name  =  Icon Drawing in 7.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Icon Drawing in 7.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 Icon Drawing in 7 - This Technical Note describes how to utilize the
built-in System 7 icon drawing utility. Use this information to better
conform to the System 7 visual human interface. Changes since May 1992. In
this Note, we replaced the C and Pascal interface files and corrected the
related text. So much text was tweaked that change bars are used only on
code changes.

 Name  =  Identifying Features.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Identifying Features.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Identifying Features - This technical note explains how to check at run
time to see if specific functionality, such as the “new” TextEdit, is
present. Applications should strive to be compatible across all
Macintoshes, but there are times when an application must have knowledge
about the machine that it is running on.  The new trap, SysEnvirons, will
give an application most of the information that it requires (what
hardware, what version of system software…).

 Name  =  Image Compr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:Image Compr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Image Compr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Image Writer IIMotio.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Image Writer IIMotio.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Image Writer II Motion - The purpose of this technical note is to answer
the many questions asked about why the paper moves the way it does on the
ImageWriter II.

 Name  =  InitGraf with MPW Assembly.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:InitGraf with MPW Assembly.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 InitGraf with MPW Assembly - The Macintosh Programmer’s Workshop (MPW)
requires assembly-language programmers to allocate their own QuickDraw
global variables rather than use the default record as indicated in Inside
Macintosh.

 Name  =  Inline Input & TextEdit.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Inline Input & TextEdit.sit
 Size: 17K         Date: 5/30/94         Version:
 Description:
 Inline Input & TextEdit - TE 27 – Inline Input for TextEdit with TSMTE
Text. Revised by -    Norbert Lindenberg    March 1994. Written by -    Yasuo Kida,
Keisuke Hara, Nobuhiro Miyatake,    December 1993. Peter Sparks, Norbert
Lindenberg. This Technical Note describes TSMTE, an extension that
simplifies implementation of inline input for TextEdit using the Text
Services Manager in System 7.1 and later, and shows you how to make the
best use of it. It also contains some advice for working with the Text
Services Manager that applies to any application using TSM, not just those
using TSMTE.

 Name  =  Inside Object Pascal.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Inside Object Pascal.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Inside Object Pascal - This Technical Note briefly explains why Object
Pascal and MacApp should only be used to write applications and MPW tools.
Although Pascal can be used to write desk accessories, drivers, XCMDs and
other types of stand–alone code, and Object Pascal is an extension of
Pascal, Object Pascal cannot be used to write anything other than an
application.  This limitation is due to the fact that Object Pascal method
dispatching relies on a valid A5 pointing to a jump table.  Because MacApp
is written in Object Pascal, this limitation applies to it as well.

 Name  =  Installer Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Installer Q&As.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 Installer Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  InternationalCha.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:InternationalCha.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 InternationalCha - The International Utilities package and the
international resources have been changed with System file 4.1 to take
advantage of the Script Manager.

 Name  =  International Canceling.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:International Canceling.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 International Canceling - This Technical Note describes potential problems
canceling operations with the Command-period key sequence and international
keyboards.

 Name  =  Internationalization.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Internationalization.sit
 Size: 33K         Date: 2/09/94         Version:
 Description:
 Internationalization - OV 20 – Internationalization Checklist. Revised by
Norbert Lindenberg    November 1993, Written by    Norbert Lindenberg    June 1993.
This checklist discusses internationalization issues that may arise with
various features that are common in Macintosh software. For each feature,
it states which problems may arise, gives advice on what to do and what not
to do, and refers you to additional reading material that can help you to
implement a world-ready solution. Changes since June 1993 - Straightened
out quotation marks in the example strings of section “String Substitution”
and some other minor bugs. Added references to new Technical Notes and
articles. Fixed description of TSMTE.

 Name  =  Internets.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Internets.sit
 Size:  5K         Date: 6/08/94         Version:
 Description:
 Internets - This Technical Note discusses how AppleTalk applications should
work across internets, groups of interconnected AppleTalk networks.  It
explains the differences between life on a single AppleTalk network and
life on an internet. Changes since March 1988. Removed the section on
AppleTalk retry timers, as it is no longer accurate.

 Name  =  Int'l Resource Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Int'l Resource Q&As.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Int'l Resource Q&A - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  ioNamePtr.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:ioNamePtr.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 ioNamePtr - It is very important to set ioNamePtr when making PB calls,
even if you don’t want  those calls to return a name. Whenever Inside
Macintosh indicates that ioNamePtr is either required for input or returns
something, you must set ioNamePtr to either nil (if you aren’t using a
name) or to point to storage for a Str255. If you don’t explicitly set
ioNamePtr, strange and unusual crashes may occur, depending on the
machine/configuration your code is run on.

 Name  =  ioPosOffset.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:ioPosOffset.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 ioPosOffset - The Device Manager chapter of Inside Macintosh Volume II says
that ioPosOffset is passed to and returned by Read and Write calls. It also
says that “After the read [or write] is completed, the position is returned
in ioPosOffset…” Actually, ioPosOffset is not changed by either call. Also
note that device drivers should only look at the dCtlPosition field of the
DCE, and should not look directly at the ioPosOffset field of the parameter
block. The Device Manager sets up dCtlPosition for the driver, taking into
account both the ioPosMode and the ioPosOffset.

 Name  =  Joy of 32-Bit Clean.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Joy of 32-Bit Clean.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Joy of 32-Bit Clean - What to do (and what not to do) to make your programs
run under A/UX and future versions of the Macintosh System Software.
Changes since October 1988:  Added information on writing 32-bit clean
CDEFs, and updated A/UX information to reflect the capabilities of A/UX
1.1.

 Name  =  Kconfig Mods for AWS95.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:Kconfig Mods for AWS95.sit
 Size:  3K         Date:11/10/93         Version:
 Description:
 Kconfig Mods for AWS95 - This technical note documents the default Kernel
parameters settings for the File/Print and Database server Configurations
under A/UX version 3.0.1 and how they are different from A/UX version 3.0.
It also describes the new configuration parameters introduced in A/UX
version 3.0.1 and their default settings.

 Name  =  Key Mapping.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Key Mapping.sit
 Size: 11K         Date:10/29/92         Version:
 Description:
 Key Mapping - This Technical Note describes the Macintosh family key code
mapping scheme when running System file 4.1 and later. This Note also
provides a “safe” method for remapping keyboards. Changes since October
1990. Added a section on how 'KMAP' resources are matched to specific ADB
keyboard types and a section on the original Macintosh and Macintosh Plus
keyboards.

 Name  =  Keybd Resource Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Keybd Resource Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Keybd Resource Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  KillNBP.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:KillNBP.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 KillNBP - This technical note clears up some confusion regarding the Name
Binding Protocol KillNBP function. The description of the PKillNBP function
on page 519 of Inside Macintosh Volume V is somewhat confusing. The data
type of the parameter thePBptr is incorrectly given as ATPPBPtr and the
pointer to the queue element from the NBP call to be aborted is incorrectly
given as being passed in aKillQEl.

 Name  =  LAP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:LAP Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 LAP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  LDEF Madness.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:LDEF Madness.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 LDEF Madness - This Technical Note uncovers a problem with writing Pascal
list definition procedures and two (yes, count  ’em, two) different methods
to work around it.

 Name  =  Large Screen Displays.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Large Screen Displays.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Large Screen Displays - A number of third-party developers have announced
large-screen display peripherals for Macintosh. One of them, Radius Inc.,
has issued a set of guidelines for developers who wish to remain compatible
with their Radius FPD; unfortunately, one of their recommendations can
cause system crashes. This note suggests a more correct approach.

 Name  =  LaserWriter Driver Surprise.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:LaserWriter Driver Surprise.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 LaserWriter Driver Surprise - This Technical Note describes some changes in
version 5.0 and later LaserWriter drivers. Changes since April 1988.
Described a bug in 5.x which is fixed in 6.0 and later, and reiterated a
warning about storing fonts in an application.

 Name  =  LaserWriter Optimization.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:LaserWriter Optimization.sit
 Size: 10K         Date: 6/22/93         Version:
 Description:
 LaserWriter Optimization - This Technical Note discusses techniques for
optimizing code for printing on the LaserWriter. Changes since March 1988,
Updated the “Printable Paper Area” and “Memory Considerations” sections as
well as the printer IDs, moved the error messages from the end of the Note
to Technical Note #161, A Printing Loop That Cares…, and removed the
“Spool-A-Page/Print-A-Page” section because Technical Note #125, Effect of
Spool-A-Page/Print-A-Page on Shared Printers, already thoroughly covers
this topic.

 Name  =  LaserWriter ROM Bugs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:LaserWriter ROM Bugs.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 LaserWriter ROM Bugs - These are LaserWriter bugs that your users may
encounter when printing from any Macintosh application. These are for your
information; you cannot code around them. The bugs described here occur in
the 1.0 and 2.0 LaserWriter ROMs.

 Name  =  LaserWriter Util Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:LaserWriter Util Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 LaserWriter Util Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Life Before 7.1.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Life Before 7.1.sit
 Size:  8K         Date: 8/26/93         Version:
 Description:
 Life Before 7.1 - Inside Macintosh-Text documents the text handling
functionality in System 7.1. This Technical Note gives you some additional
information that lets you design software using Inside Macintosh-Text and
make it work on system software before System 7.1, going back to System
6.0.7.

 Name  =  Life With Font/DA Mover.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Life With Font/DA Mover.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Life With Font/DA Mover - This technical note describes how to make sure
that your desk accessory will work after being moved by Font/Desk Accessory
Mover.

 Name  =  List Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:List Mgr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 List Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Little PowerBook Sleep.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Little PowerBook Sleep.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Little PowerBook Sleep - The purpose of this Note is to describe the
ramifications of resting, sleeping, and power-saving modes in the PowerBook
family of Macintosh computers, how they may affect your application, and
the appropriate ways to defeat them, when appropriate. It also describes
some nonintuitive ramifications of working with a battery-powered computer.

 Name  =  Loading Components Bug.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:Loading Components Bug.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 Loading Components Bug - The Component Manager may change the current
resource file in the resource search path. This is a bug and will be fixed
as soon as possible.

 Name  =  Lock, Unlock the Range.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Lock, Unlock the Range.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Lock, Unlock the Range - This Technical Note discusses the _PBLockRange and
_PBUnlockRange routines; how they act on local and shared volumes and why
you should not set the ioPosMode field to fsFromLEOF in the parameter block
for those routines when accessing a file on an AppleShare volume. Changes
since April 1988. Added information on how _PBLockRange and _PBUnlockRange
really work.

 Name  =  Low-Level Printing.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Low-Level Printing.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Low-Level Printing - When you use the low-level printer driver to print,
you don’t get the benefits of the error checking that is done when you use
the high-level Printing Manager. So, if the user prints to an AppleTalk
ImageWriter (including an AppleTalk ImageWriter LQ) that is busy printing
another job, the driver doesn’t know whether the printer is busy, offline,
or disconnected.  Because of this, PrError will return (and PrintErr will
contain) abortErr.

 Name  =  MIDI Interface Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:MIDI Interface Q&As.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 MIDI Interface Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MPP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:MPP Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 MPP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MPW -mc68881.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW -mc68881.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 MPW -mc68881 - This Technical Note discusses MPW’s -mc68881 option, which
represents Extended values in 96 bits (instead of 80, as with software
SANE), and compatibility issues when using non-SANE system calls that
expect 80-bit Extended values. Changes since June 1990. Extended the
warning about explicitly checking for the presence of an FPU if an
application uses floating-point instructions to include the possibility of
FPU-less MC68040 products and also raised the issue of extended values
embedded in data structures.

 Name  =  MPW 2.0.2 Bugs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW 2.0.2 Bugs.sit
 Size: 16K         Date:10/29/92         Version:
 Description:
 MPW 2.0.2 Bugs - This Technical Note describes latest information about
bugs or unexpected “features” in the MPW C, Pascal, and Assembler products
and the Toolbox and OS Interface Libraries.  We intend this Note to be a
complete list of all known bugs in these products, which will be updated as
old bugs are fixed, or new ones appear.  If you have encountered a bug or
unexpected feature which is not described here, be sure to let us know.
Specific code examples are useful.

 Name  =  MPW Assembly Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW Assembly Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 MPW Assembly Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MPW C++ Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW C++ Q&As.sit
 Size: 17K         Date:10/29/92         Version:
 Description:
 MPW C++ Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  MPW C Functions.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW C Functions.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 MPW C Functions - Here’s the low-down on when C functions need not be
declared in include files.

 Name  =  MPW C Glue for Point & Stri.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW C Glue for Point & Stri.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 MPW C Glue for Point & Stri - MPW 2.0 includes new C interfaces to ROM
routines which no longer do string and point conversions. These new
interfaces are described here.

 Name  =  MPW C Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW C Q&As.sit
 Size: 23K         Date:10/29/92         Version:
 Description:
 MPW C Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MPW {$LOAD}.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW {$LOAD}.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 MPW {$LOAD} - This technical note discusses the Pascal {$LOAD} directive as
well as how to unload the _DataInit and %_MethTables segments.

 Name  =  MPW Library Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW Library Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 MPW Library Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MPW Pascal Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW Pascal Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 MPW Pascal Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MPW Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 MPW Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MPW Tool Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MPW Tool Q&As.sit
 Size: 16K         Date:10/29/92         Version:
 Description:
 MPW Tool Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  MacApp Bugs 3.0.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MacApp Bugs 3.0.sit
 Size: 38K         Date:10/29/92         Version:
 Description:
 MacApp Bugs 3.0 - This Technical Note describes the latest information
about bugs or unexpected “features” in MacApp.  Where possible, solutions
and fixes are noted.  DTS intends this Note to be a complete list of all
known bugs in MacApp and will update it as old bugs are fixed or new ones
appear.  If you have encountered a bug or unexpected feature which is not
described here, be sure to let DTS know. Specific code examples and
suggested fixes are useful.

 Name  =  MacApp Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MacApp Q&As.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 MacApp Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MacApp Segmentation.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MacApp Segmentation.sit
 Size: 14K         Date:12/29/92         Version:
 Description:
 MacApp Segmentation - This Technical Note describes MacApp segmentation
strategies and guidelines. It also describes performance, runtime, and
development tools issues related to segmentation. Some of the discussion is
also relevant to general segmentation strategies with non-MacApp-based
applications. The MacApp techniques are based on MacApp 3.0; however, many
of the issues are also relevant to MacApp 2.0.

 Name  =  MacApp 'View'.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MacApp 'View'.sit
 Size: 19K         Date:10/29/92         Version:
 Description:
 MacApp 'View' - This Technical Note describes the new MacApp 3.0 'View'
resource.

 Name  =  MacClassic,LC,IIsiRAM.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Mem Config:MacClassic,LC,IIsiRAM.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Mac Classic, LC, IIsi RAM - drawings on RAM install configurations.

 Name  =  Mac Common LISP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Mac Common LISP Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Mac Common LISP Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Mac II Board Suppliers.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac II Board Suppliers.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Mac II Board Suppliers - This note lists suppliers of parts that may be
helpful for Macintosh II board developers. If your company supplies these
parts, but is not listed here, please send a message to us (at the address
on Technical Note #0) and we’ll include you in the next revision of this
technical note.

 Name  =  Mac IIfx Inside Story.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac IIfx Inside Story.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Mac IIfx Inside Story - This Technical Note addresses various areas of
potential incompatibilities with the Macintosh IIfx and current software
applications and provides information about some of Apple’s compatibility
software updates.

 Name  =  Mac IIfx RAM.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Mem Config:Mac IIfx RAM.sit
 Size: 14K         Date: 6/22/93         Version:
 Description:
 Mac IIfx RAM - drawings on RAM install configurations.

 Name  =  Mac Mem Configurations.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:Mac Mem Configurations.sit
 Size:126K         Date:12/28/92         Version:
 Description:
 Mac Mem Configurations - This Technical Note describes the different
possible memory configurations of all models of the Macintosh family that
use Single In-line Memory Modules (SIMMs) as well as the non-SIMM memory
upgrade options of the Macintosh Portable, Macintosh Classic, and Macintosh
PowerBooks. (Special thanks to Brian Howard for the Macintosh Plus and
original SE drawings, and for the inspiration for the other drawings.) This
Note also describes the obstacles to using four megabit (Mbit) DRAM SIMMs
in Apple Macintosh products to date.

 Name  =  MacPaint Document Format.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MacPaint Document Format.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 MacPaint Document Format - This Technical Note describes the internal
format of a MacPaint® document, which is a standard used by many other
programs.  This description is the same as that found in the “Macintosh
Miscellaneous” section of early Inside Macintosh versions. Changes since
October 1988. Fixed bugs in the example code.

 Name  =  Mac Plus RAM.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Mem Config:Mac Plus RAM.sit
 Size: 14K         Date: 6/22/93         Version:
 Description:
 Mac Plus RAM - drawings on RAM install configurations.

 Name  =  Mac Portable PDS Developmen.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Portable PDS Developmen.sit
 Size: 13K         Date: 6/22/93         Version:
 Description:
 Mac Portable PDS Development - The Technical Note describes the unique
aspects of the Macintosh Portable Processor Direct Slot (PDS), including
the severe limitations in its use.

 Name  =  Mac Portable ROM Expansion.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Portable ROM Expansion.sit
 Size: 13K         Date: 6/22/93         Version:
 Description:
 Mac Portable ROM Expansion - This Technical Note explains the practice of
and theory behind compatible use of the expansion ROM in the Macintosh
Portable.

 Name  =  Mac Quadra Built-In Video.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Quadra Built-In Video.sit
 Size: 11K         Date: 6/22/93         Version:
 Description:
 Mac Quadra Built-In Video - This is an in-depth article in three parts,
describing the internal video on the Macintosh Quadra computers. The first
part discusses a number of general Quadra video topics, the second part
details how to wire the video connector sense pins to access all the
Quadra’s supported video modes, and the third describes the memory
configurations necessary to support each of the video modes at specific
pixel depths.

 Name  =  Mac SE (w/jump) RAM.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Mem Config:Mac SE (w/jump) RAM.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 Mac SE (w/jump) RAM - drawings on RAM install configurations.

 Name  =  MacSE/30, II, IIx RAM.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Mem Config:MacSE/30, II, IIx RAM.sit
 Size: 11K         Date: 6/22/93         Version:
 Description:
 Mac SE/30, II, IIx RAM - drawings on RAM install configurations.

 Name  =  Mac SE RAM.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Mac Mem Config:Mac SE RAM.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 Mac SE RAM - drawings on RAM install configurations.

 Name  =  MacTCP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:MacTCP Q&As.sit
 Size: 17K         Date:10/29/92         Version:
 Description:
 MacTCP Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MacWorkstation Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:MacWorkstation Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 MacWorkstation Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MacinTalk Final Chapter.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MacinTalk Final Chapter.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 MacinTalk Final Chapter - This Technical Note discusses the MacinTalk
software product.

 Name  =  Macintosh 21" Color Display.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Macintosh 21" Color Display.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 Macintosh 21" Color Display - This Technical Note presents the technical
specifications for the Macintosh 21" Color Display with the objective of
allowing display board and accelerator board manufacturers to ensure
compatibility with this monitor.

 Name  =  Macintosh Allegro Common Li.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Macintosh Allegro Common Li.sit
 Size: 11K         Date: 6/22/93         Version:
 Description:
 Macintosh Allegro Common - This Technical Note describes some known
problems and provides solutions to these problems for the Macintosh Allegro
Common Lisp™ package which is available from Apple Computer, Inc.  You
should note, however, that although Apple acquired Coral Software and is
selling Macintosh Allegro Common Lisp, Apple is not currently distributing
any other products which had been developed or previously sold by Coral
Software.

 Name  =  Macintosh Plus ROMs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Macintosh Plus ROMs.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Macintosh Plus ROMs - Readers Digest condensed version of Macintosh Plus
ROM history, or the truth according to Bo3bdar the everpresent.

 Name  =  Macintosh SE/30.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Macintosh SE/30.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Macintosh SE/30 - This Technical Note discusses the Macintosh SE/30, items
of interest to developers, and sources for further information. Changes
since April 1989. Corrected an error in the addresses of the video display
buffers. The Macintosh SE/30 is a modification of the original Macintosh SE
concept. The SE/30 combines the modularity of the original SE with the
capabilities of the larger Macintosh IIx.  Although the name implies that
the SE/30 borrows many characteristics from the SE, there are actually
substantial differences between the two machines, and this Note addresses
some of those differences.

 Name  =  MacsBug Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:MacsBug Q&As.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 MacsBug Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Managerial Abuse.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Managerial Abuse.sit
 Size: 11K         Date:10/29/92         Version:
 Description:
 Managerial Abuse - When using the various pieces of the Macintosh operating
system there is a temptation to try to stretch the built-in Managers too
far. Developers should be aware of the intended purpose of the various
Managers and beware of using them for things that they were not designed to
handle. If extended beyond their design goals, they will become slow and
unwieldy.

 Name  =  Math Function Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:Math Function Q&As.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Math Function Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MaxApplZone and MoveHHi.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:MaxApplZone and MoveHHi.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 MaxApplZone and MoveHHi - When calling MaxApplZone and MoveHHi from
assembly language, be sure to get the correct code.

 Name  =  Mem Mgr Compatibilit.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:Mem Mgr Compatibilit.sit
 Size:  7K         Date: 8/26/93         Version:
 Description:
 Mem Mgr Compatibilit - The Memory Manager has been rewritten for the
PowerPC Macintosh computers. This new Memory Manager runs native PowerPC
code and uses better algorithms. With this new Memory Manager, there are
both old and new restrictions on it use. Topics - A list of things not to
do; A new list of restrictions for being compatible in the future, A list
of recommendations.

 Name  =  Memory H/W Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Memory H/W Q&As.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Memory H/W Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Memory Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:Memory Mgr Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Memory Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Memory Mgt Ov Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:Memory Mgt Ov Q&As.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Memory Mgt Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Menu Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Menu Mgr Q&As.sit
 Size: 25K         Date:10/29/92         Version:
 Description:
 Menu Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Misc Tool Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Misc Tool Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Misc Tool Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Mixing HFS and C I/O.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Mixing HFS and C I/O.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Mixing HFS and C I/O - This Technical Note discusses the problem of mixing
calls to the Macintosh file system with calls to MPW C library file I/O
routines. Problems with Communication Between HFS and C. Frequently,
developers want to use both Macintosh file I/O and C file I/O.  Developers
who do this must keep in mind that they are combining two distinct file
representations (the Macintosh and ANSI C). The only limitation on mixing
HFS and C I/O functions is that they cannot be mixed on the same open file.
There are three reasons why this cannot be done.

 Name  =  Modem Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Modem Q&As.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Modem Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Modifying Standard String C.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Modifying Standard String C.sit
 Size: 11K         Date: 6/22/93         Version:
 Description:
 Modifying Standard String C - This technical note describes how to modify
the standard string comparison by constructing an itl2 resource. Developers
may want to modify the standard string comparison if Apple’s comparison
doesn’t meet their needs or if Apple has not written a string comparison
routine for the language that concerns them.

 Name  =  Monitor Depth.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Monitor Depth.sit
 Size:  7K         Date: 6/22/93         Version:
 Description:
 Monitor Depth - This Technical Note describes two new system calls that
allow an application to change the depth and flags for a given device and
also check whether a device supports a particular depth and flags setting.
Apple provides these calls to give developers a better way to help users
make changes when they consider it appropriate. Abusive use of these calls
is a sure way to guarantee that the Thought Police come after you to
confiscate your Macintoshes, your stock of Mountain Dew®, and your
Technical Notes binder. This Note assumes familiarity with Inside
Macintosh, Volume V, Graphics Devices.

 Name  =  MoreMasters Revisited.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:MoreMasters Revisited.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 MoreMasters Revisited - MoreMasters should be called from CODE segment 1.
The number of master pointers that a program needs can be determined
empirically. MoreMasters can be tricked into creating the exact number of
master pointers desired.

 Name  =  Movable Modal Dialogs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Movable Modal Dialogs.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Movable Modal Dialogs - This Technical Note describes the process by which
an application can remap the Help Manager 'hmnu' resource while a movable
modal dialog box is on the screen. The Help Manager handles the case for
modal dialog boxes but punts in the case of movable modal dialog boxes. The
following information will help you get the correct interface performance.

 Name  =  MoveHHi and SetResPurge.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:MoveHHi and SetResPurge.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 MoveHHi and SetResPurge - SetResPurge(TRUE) is called to make the Memory
Manager call the Resource Manager before purging a block specified by a
handle. If the handle is a handle to a resource, and its resChanged bit is
set, the resource data will be written out (using WriteResource). When
MoveHHi is called, even though the handle’s block is not actually being
purged, the resource data specified by the handle will be written out. An
application can prevent this by calling SetResPurge(FALSE) before calling
MoveHHi (and then calling SetResPurge(TRUE) after the MoveHHi call).

 Name  =  Movie Toolbox Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:Movie Toolbox Q&As.sit
 Size: 21K         Date:10/29/92         Version:
 Description:
 Movie Toolbox Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Movies ‘LOOP’ Atom and Frie.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:Movies ‘LOOP’ Atom and Frie.sit
 Size:  6K         Date:12/28/92         Version:
 Description:
 Movies ‘LOOP’ Atom and Friends - This Technical Note discusses entertaining
uses for QuickTime user data atoms, Apple defined and otherwise.

 Name  =  MultiFinder FAQ.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:MultiFinder FAQ.sit
 Size:  9K         Date:12/27/93         Version: FAQ
 Description:
 MultiFinder FAQ - New Technical Notes - This technical note provides
answers to some of the more frequently asked questions about MultiFinder.
The development name for MultiFinder was Juggler, so the term "juggle" is
used in this technical note to denote a context switch. Some questions for
which answers are given - How can I tell if WaitNextEvent is implemented?
How can I tell if the MultiFinder Temporary Memory Allocation calls are
implemented? How can I tell if my application is running in the background?
When exactly does juggling take place? Can I disable suspend/resume events
by passing the appropriate event mask to WNE/GNE/EventAvail? Should my
application use WaitNextEvent? and more!

 Name  =  MultiFinder Miscellanea.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:MultiFinder Miscellanea.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 MultiFinder Miscellanea - This Technical Note discusses MultiFinder issues
of which programmers should be aware. Changes since June 1988. Updated and
generalized sample code to reflect new MPW 3.0 calls in both C and Pascal
for saving and restoring A5 for interrupt code that accesses application
globals.  Removed text that can be found in Programmer’s Guide to
MultiFinder, and added a note about _PostEvent.

 Name  =  MultiFinder Questions.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:MultiFinder Questions.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 MultiFinder Questions - This technical note provides answers to some of the
more frequently asked questions about MultiFinder. The development name for
MultiFinder was Juggler, so the term “juggle” is used in this technical
note to denote a context switch.

 Name  =  MultiFinder Revisited.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:MultiFinder Revisited.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 MultiFinder Revisited - This Technical Note describes several new features
found in MultiFinder 6.0 and answers a few more commonly-asked questions.
Changes since December 1989. Added a warning to the section on
childDiedEvents about distribution of MultiFinder 6.1bx.

 Name  =  MultiFinder and _SetGrowZon.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:MultiFinder and _SetGrowZon.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 MultiFinder and _SetGrowZon - MultiFinder patches the _SetGrowZone trap,
and this patch can cause your program to crash if you attempt to save and
restore the grow zone procedure.

 Name  =  Multiple Inheritance.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Multiple Inheritance.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Multiple Inheritance - This Technical Note answers a common question about
MPW C++:  “Why doesn’t HandleObject support multiple inheritance?”  It does
this by giving a brief overview of how multiple inheritance is implemented
in MPW C++.

 Name  =  My Life as a Pascal Object.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:My Life as a Pascal Object.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 My Life as a Pascal Object - This Technical Note discusses the PascalObject
base class, used, for instance, with MacApp programming. The Technical Note
describes how to write PascalObject derived classes that work with both
Object Pascal and C++ code linking. It also describes the current
restrictions and bugs with writing C++ code using PascalObject as the base
class. This Technical Note is based on MacApp 2.0(.1), MPW 3.2 and MPW C++
3.1.

 Name  =  NBP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:NBP Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 NBP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Networking Cards & SNMP.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Networking Cards & SNMP.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 Networking Cards & SNMP - Apple provides an SNMP Manager that implements an
architecture for doing network management on a Macintosh computer. This
Tech Note describes how the SNMP manager finds network cards on a Macintosh
and explains how you can make the SNMP Manager recognize new types of
network cards. This Tech Note is a supplement to the information provided
in the Developers kit for SNMP available on the E.T.O. CD-ROM in the
MacSNMP Programmer’s Guide.. The kit defines the interfaces to actually
gather the information.

 Name  =  New CDEV Messages.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:New CDEV Messages.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 New CDEV Messages - This Technical Note describes some previously
undocumented messages that the Control Panel can send to a Control Panel
device (cdev).

 Name  =  New Memory Manager.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:New Memory Manager.sit
 Size: 10K         Date: 2/09/94         Version:
 Description:
 New Memory Manager - The New Memory Manager and You. This Technical Note
describes changes in the Modern Memory Manager that you need to be aware
of. Specifically take note of the changes to the bus error handlers in the
first section. Topics - Bus Error Handlers in the New Memory Manager, Bus
Error Return Value Changes, Free Block Miscellanea, A5 World Problems and
Heap Callback Procedures. The introduction of the PowerPC Macintosh also
introduces a new Memory Manager. Many of the splendid features of this new
implementation have already been discussed in tech note Memory 13. Weary
travelers may have noted some strange behavior though, and this note
attempts to answer most of the remaining big questions you may have.

 Name  =  New Resource Manager Calls.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:New Resource Manager Calls.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 New Resource Manager Calls - This Technical Note describes two new Resource
Manager calls that make opening and creating resource files much easier.

 Name  =  Notification Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Processes:Notification Mgr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Notification Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Notification Manager.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Notification Manager.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Notification Manager - This Technical Note describes the Notification
Manager, the part of the operating system that lets an application, desk
accessory, or driver alert the user. Changes since October 1989. Clarified
the section on error handling for calls to _NMInstall.

 Name  =  NuBus Block Transfers.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:NuBus Block Transfers.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 NuBus Block Transfers - This Technical Note describes the sResource entries
needed in a declaration ROM to inform NuBus™ masters when a board is
capable of receiving or sending block transfers. In addition to normal long
word transfers, the NuBus specification defines a number of block transfer
transactions. In block mode transfers, the system arbitrates for the bus a
single time and then performs a group of consecutive long word transfers
before releasing the bus. The reduction in bus arbitration time can result
in considerable gains in performance.

 Name  =  NuBus Interrupt Latency.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:NuBus Interrupt Latency.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 NuBus Interrupt Latency - This Technical Note discusses NuBus™ interrupt
latency, and why, contrary to popular belief, the Macintosh is not a
real-time machine. Changes since December 1988. Changed sample code to
defer cursor rendering to a deferred task rather than a “pseudo-VBL” task.
The Macintosh is not a real-time machine.  The Macintosh does not support
DMA. There are many variables in the Macintosh that make it impossible to
deterministically figure out exactly when things are going to happen.
Despite these facts, there are those who must push the envelope. For these
courageous adventurers, we provide the following information in the hope
that it speeds your journey.

 Name  =  NuBus Physical Designs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:NuBus Physical Designs.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 NuBus Physical Designs - This Technical Note discusses the possible
problems you might run into while designing a NuBus™ card. It covers some
of the specifications which, if not followed, will have problems with
current Macintosh machines, and possibly future machines. Changes since
June 1989. Added warnings about the no component area and full-size NuBus
cards.

 Name  =  NuBus Power Limits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:NuBus Power Limits.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 NuBus Power Limits - This Technical Note discusses a very real power limit
for NuBus™ expansion cards and warns developers to heed this limit lest
they want users trashing their machines by overextending the Macintosh
power supply.

 Name  =  NuBus Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:NuBus Q&As.sit
 Size: 19K         Date:10/29/92         Version:
 Description:
 NuBus Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Nulls in Filenames.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Nulls in Filenames.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Nulls in Filenames - Some applications (loosely speaking so as to include
Desk Accessories, INITs, and what-have-you) generate or rename special
files on the fly so that they are not explicitly named by the user via
SFPutFile. Since the Macintosh file system is very liberal about filenames
and only excludes colons from the list of acceptable characters, this can
lead to some difficulties, both for the end user and for writers of other
programs which may see these files.

 Name  =  Number of Resources.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Number of Resources.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Number of Resources - This note describes the limitation of the number of
resources in a single resource file.

 Name  =  OS Queue Utility Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:OS Queue Utility Q&As.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 OS Queue Utility Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Object Pascal.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Object Pascal.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Object Pascal - Object Pascal must have a CODE segment named %_MethTables
in order to access object methods. In MacApp this is taken care of “behind
the scenes” so you don’t have to worry about it . However, if you are doing
a straight Object Pascal program, you must make sure that %_MethTables is
around when you need it. If it’s unloaded when you call a method, your
Macintosh will begin executing wild noncode and die a gruesome and horrible
death.

 Name  =  Off-Screen Bitmaps.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Off-Screen Bitmaps.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Off-Screen Bitmaps - This Technical Note provides an example of creating an
off-screen bitmap, drawing to it, and then copying from it to the screen.
Changes since April 1990. Clarified the section on window updates with
off-screen bitmaps to explicitly limit these updates to your own windows.

 Name  =  Old Style Colors.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Old Style Colors.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Old Style Colors - This Technical Note covers limitations of the original
Macintosh color model (eight-color) which Inside Macintosh, Volume I-173,
QuickDraw does not document. Changes since October 1989. Added definitions
of the old-style constants.

 Name  =  OmegaSANE.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:OmegaSANE.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 OmegaSANE - System 7.0.1 introduced a new version of SANE (the Standard
Apple Numerics Environment) known as OmegaSANE.  This Note discusses the
features of OmegaSANE and the associated compatibility risks.

 Name  =  OpenRFPerm.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:OpenRFPerm.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 OpenRFPerm - This note corrects an error in the description of the Resource
Manager routine OpenRFPerm found in Inside Macintosh Volume IV.

 Name  =  Opening AppleTalk.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Opening AppleTalk.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Opening AppleTalk - This Technical Note describes the most effective, safe,
and compatible way to open the AppleTalk drivers, .MPP and .ATP. The
process of opening the AppleTalk drivers, .MPP and .ATP, can be greatly
simplified.  The AppleTalk Manager chapters of Inside Macintosh describe
the calls MPPOpen and ATPLoad for use by high-level languages.  They also
describe the process of examining low-memory globals SPConfig and PortBUse
before calling _Open for assembly language use of AppleTalk.

 Name  =  Opening Serial Driver.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Opening Serial Driver.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Opening Serial Driver - This Technical Note describes the recommended,
safe, and compatible way to open the Macintosh serial driver, and it
explains why you should no longer check for port availability. Changes
since October 1989. Corrected syntax errors in the sample code.

 Name  =  Our Checksum Bounced.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Our Checksum Bounced.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Our Checksum Bounced - This Technical Note discusses a fix to a SCSI
Manager bug which concerns all developers working with SCSI and NuBus™
device drivers.

 Name  =  Owned Resource Shortcuts.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Owned Resource Shortcuts.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Owned Resource Shortcuts - To allow the Font/DA Mover to renumber desk
accessories as needed when moving them between system files, desk
accessories should use the “owned resource” protocol described in the
Resource Manager chapter of Inside Macintosh Volume I.

 Name  =  PAP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:PAP Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 PAP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  PAP Status Buffer.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:PAP Status Buffer.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 PAP Status Buffer - This Technical Note shows the format of the ATP data
part of Printer Access Protocol (PAP) OpenConnReply and Status AppleTalk
response packets. A PAP client returns this information in its
implementation of the PAPStatus and PAPOpen calls. The status buffer format
is shown for both LaserWriter and ImageWriter (with the ImageWriter II/LQ
LocalTalk Option card installed) printers.

 Name  =  PBCatMove - Moving Your Cat.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:PBCatMove - Moving Your Cat.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 PBCatMove - Moving Your Cat - This Technical Note clarifies the
documentation in Inside Macintosh for _PBCatMove and provides a
demonstration on how to use it. Changes since February 1989, Added a
discussion of using NIL for the destination name pointer, which is the
simplest way to use _CatMove, and revised the sample code to use the
high-level File Manager calls.  Thanks to Tim Dierks of Apple Developer
Technical Support U.K. for pointing out the problems with the previous
version of this Note.

 Name  =  PBClose the Barn Door.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:PBClose the Barn Door.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 PBClose the Barn Door - This Technical Note discusses the need for
Macintosh device drivers to implement _PBClose. You may get the idea when
implementing device drivers that _PBClose is superfluous.  After all, if
you have a resident driver for a NuBus™ video board, the only time your
driver is not needed is if the operating system is going away.  It might
seem that nothing important can happen after the operating system goes
away, so why bother with _PBClose?  Well, it turns out a lot can happen,
and this Note tells you why it is important to implement a Close (_PBClose)
routine.

 Name  =  PBGetCatInfo&ioFDirIndex.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:PBGetCatInfo&ioFDirIndex.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 PBGetCatInfo&ioFDirIndex - This technical note describes how to set
ioFDirIndex for PBGetCatInfo. The File Manager chapter of Inside Macintosh
volume IV is not very specific in describing how to use ioFDirIndex when
calling PBGetCatInfo. It correctly says that ioFDirIndex should be positive
if you are making indexed calls to PBGetCatInfo (analogous to making
indexed calls to PBGetVInfo as described in Technical Note #24).

 Name  =  PBHSetVol.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:PBHSetVol.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 PBHSetVol - This note explains PBHSetVol, and why its use is not
recommended. PBHSetVol, like SetVol and PBSetVol, allows you to set the
current default volume and directory to be used with subsequent File
Manager calls. Unlike SetVol and PBSetVol, though, PBHSetVol lets you
specify the volume and the directory separately, using the ioVRefNum and
ioWDDirID fields.

 Name  =  PBShare & PBUnshare.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:PBShare & PBUnshare.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 PBShare & PBUnshare - This Technical Note documents three new File Manager
routines available on shared local volumes. The Pascal glue code, C glue
code, and the assembler equates and macros for the calls are included in
this note. Changes since October 1991. Corrected ioObjType input values for
PBGetUGEntry.

 Name  =  PDS Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:PDS Q&As.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 PDS Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  PIdle Procedure.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:PIdle Procedure.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 PIdle Procedure - This Technical Note discusses how to defensively program
a pIdle procedure to work with the majority of print drivers in existence
today, and how to install it at print time.

 Name  =  PPC Toolbox Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Interapplication Comm.:PPC Toolbox Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 PPC Toolbox Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  PackBits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:PackBits.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 PackBits - This Technical Note describes the format of data packed by the
Toolbox utility _PackBits and documents a change to the srcBytes limit and
possible worst case. Although you can simply unpack this data using
_UnPackBits, Apple provides this information for the terminally curious and
for those manipulating MacPaint® documents or PICT files by hand. Warning:
This format information is subject to change. Changes since November 1990.
A warning has been added about the handling of a flag-counter byte value of
-128.

 Name  =  Palette Manager Changes 6.0.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Palette Manager Changes 6.0.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Palette Manager Changes 6.0 - This Technical Note describes the changes and
enhancements to the Palette Manager in System Software 6.0.2 and future
versions.

 Name  =  Palette Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Palette Mgr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Palette Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Parameters for MDEF Message.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Parameters for MDEF Message.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 Parameters for MDEF Message - In order to support popup menus, menu
definition procedures (MDEFs) must now respond to a new message, mPopupMsg.
mPopupMsg is message number 3. When your MDEF is called with this message,
it should calculate the rectangle in which the popup menu should appear.

 Name  =  Pascal RoutiP.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Pascal RoutiP.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Pascal RoutiP - Routines passed by pointer are used in many places in
conjunction with Macintosh system routines. For example, filter procedures
for modal dialogs are passed by pointer, as are controls’ action procedures
(when calling TrackControl), and I/O completion routines.

 Name  =  Pascal to C PROC Parms.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Pascal to C PROC Parms.sit
 Size: 13K         Date:10/29/92         Version:
 Description:
 Pascal to C PROC Parms - This Technical Note talks about nested procedures
and PROCEDURE parameters in Pascal and what to do when converting them into
C or C++. Changes since February 1990. Fixed some type coercion problems.

 Name  =  Pending Update Perils.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Pending Update Perils.sit
 Size: 14K         Date: 6/22/93         Version:
 Description:
 Pending Update Perils - This Technical Note discusses potential problems
when pending update events for windows behind modal dialogs are not
serviced.  This note also documents some new System 7 Dialog Manager calls.

 Name  =  Performance Tuning.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Performance Tuning.sit
 Size: 20K         Date:10/29/92         Version:
 Description:
 Performance Tuning - This Technical Note is a collection of useful ideas
and suggestions to help you decrease the time required to compile and link
under MPW. Some of the issues are even relevant to any development tools
running under the Macintosh environment. The Tech Note will also clarify
what performance tunings work, and which are marginal or may not work at
all.

 Name  =  PictComments Real Deal.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:PictComments Real Deal.sit
 Size: 35K         Date:10/29/92         Version:
 Description:
 PictComments Real Deal - Changes since March 1988:  This Note (formerly
titled “Optimizing for the LaserWriter—PicComments”) describes the picture
comments defined and interpreted by the Apple printer drivers. Most of the
picture comments are specific to PostScript, but we renamed the Note to
emphasize that LaserWriter printers are not necessarily PostScript devices,
and that QuickDraw printer drivers may implement their own picture comment
handling. This Note has been completely rewritten and incorporates all
additional insights gained during the last few years.

 Name  =  Picture Utility Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Picture Utility Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Picture Utility Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Pictures and Clip Regions.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Pictures and Clip Regions.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Pictures and Clip Regions - This note describes a problem that affects
creation of QuickDraw pictures. When a GrafPort is created, the fields in
the GrafPort are given default values; one of these is the clip region,
which is set to the rectangle (–32767, –32767, 32767, 32767). If you create
a picture, then call DrawPicture with a destination rectangle that is not
the same size as the picFrame without ever changing the default clip
region, nothing will be drawn.

 Name  =  Pictures and Print.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Pictures and Print.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Pictures and Print - This technical note described some problems and
features of using Quickdraw pictures with the Printing Manager.  In
general, if your application prints Quickdraw pictures, you should read
this note.

 Name  =  Pinouts.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Pinouts.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Pinouts - This note gives pinouts for Macintosh ports, cables, and other
products.

 Name  =  Plotting Small Icons.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Plotting Small Icons.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Plotting Small Icons - This Technical Note discusses the 'SICN' resource
format and how to plot one in a GrafPort. Changes since August 1989.
Corrected errors in the Pascal code and spruced up the rest.

 Name  =  Position ind PS.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Position ind PS.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Position ind PS - This technical note describes a method for inserting
position-independent PostScript into QuickDraw pictures. There is a problem
with pictures that contain PostScript code. Sometimes the PostScript code
that is inserted into the picture is dependent on the position of the
picture on the page. The problem arises when these pictures are cut or
copied from their original position, and pasted into another position or
even into another document. The PostScript code will not know the new
location of the picture, and will not execute correctly.

 Name  =  PostScript Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:PostScript Q&As.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 PostScript Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  PowerBook Miscellanea.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:PowerBook Miscellanea.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 PowerBook Miscellanea - This Technical Note describes some nonintuitive
ramifications of working with a battery-powered computer.

 Name  =  Power Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Power Mgr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Power Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Power Supply Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Power Supply Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Power Supply Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  PrGeneral.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:PrGeneral.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 PrGeneral - The Printing Manager architecture has been expanded to include
a new procedure called PrGeneral. The features described here are advanced,
special-purpose features, intended to solve specific problems for those
applications that need them. The calls to determine printer resolution
introduce a good deal of complexity into the application’s code, and should
be used only when necessary.

 Name  =  Principia Off-Screen.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Principia Off-Screen.sit
 Size: 58K         Date:10/29/92         Version:
 Description:
 Principia Off-Screen - Using Color QuickDraw to draw off screen is a common
requirement of applications and other kinds of programs that run on the
Macintosh. This Note discusses what Color QuickDraw needs in a graphics
environment and how to create one for off-screen drawing. A brief
discussion of GWorlds, which are off-screen graphics environments that are
set up by the system, is given to help you decide whether to use them or
the do-it-yourself techniques described in this Note for setting up an
off-screen graphics environment.

 Name  =  Print Dialogues - Adding It.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Print Dialogues - Adding It.sit
 Size: 15K         Date: 6/22/93         Version:
 Description:
 Print Dialogues - Adding It - This technical note discusses how to add your
own items to the Printing Manager’s dialogs.

 Name  =  PrintMonitor Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:PrintMonitor Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 PrintMonitor Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Printer Driver Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Printer Driver Q&As.sit
 Size: 27K         Date:10/29/92         Version:
 Description:
 Printer Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Printing Loop Cares.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Printing Loop Cares.sit
 Size: 13K         Date: 2/09/94         Version:
 Description:
 Printing Loop Cares - A Printing Loop that Cares - This Technical Note
discusses opening and closing the Printing Manager with calls to _PrOpen
and _PrClose as well as how to handle errors at print time. Changes since
October 1990 - Added code in both versions to handle printing documents
larger than 128 pages. Introduction - At one time, Apple recommended that
developers call _PrOpen at the beginning of their application and _PrClose
at the end, before returning to the Finder. This recommendation was in the
ancient past when an application only had to deal with a single printer
driver. As more printer drivers became available, it became important for
an application to consider the presence of other applications.

 Name  =  Problem with GetVInfo.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Problem with GetVInfo.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Problem with GetVInfo - The high-level call GetVInfo (and its low-level
counterpart PBGetVInfo) may return inaccurate results for freeBytes when
running HFS. The high-level File Manager call GetVInfo returns the number
of free bytes on a volume as one of its parameters. Since GetVInfo is
really only glue that fills in a parameter block for you and then calls
PBGetVInfo, the values returned from it are subject to the limitations
(imposed for MFS) discussed in the File Manager chapter of Inside Macintosh
Volume IV.

 Name  =  Process Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Processes:Process Mgr Q&As.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Process Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Process Overview Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Processes:Process Overview Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Process Overview Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Processor Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Processor Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Processor Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Programmatic PostScript.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Programmatic PostScript.sit
 Size: 10K         Date:12/28/92         Version:
 Description:
 Programmatic PostScript - This Technical Note discusses how to make the
LaserWriter driver, versions 7.0 and later, create PostScript files from
your printing loop, and when this is and is not appropriate.

 Name  =  Projector Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Projector Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Projector Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  pslt resource.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:pslt resource.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 pslt resource - One of the new resources that can be very helpful to some
NuBus™ developers is the 'pslt' resource. The only problem is that the
resource is not documented. This Technical Note takes care of the
documentation problem.

 Name  =  PurgeProc Note.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:PurgeProc Note.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 PurgeProc Note - This Technical Note discusses the use of the purgeProc
field of an application’s heap zone. Most applications will never need to
use a purgeProc. However, if your application requires the ability to
maintain purgeable handles containing data, or you need to have special
notification when a certain handle is purged, a purgeProc might help you.

 Name  =  QuickTime 1.6.1.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:QuickTime 1.6.1.sit
 Size: 26K         Date: 5/30/94         Version:
 Description:
 QuickTime 1.6.1 - QT 4 - QuickTime 1.6.1 Features. Written by -    Angus,
Peter Hoddie, and the QuickTime Team    June, 1993. This Note is a technical
discussion of the changes between QuickTime 1.5 and QuickTime 1.6.1.
QuickTime 1.6.1 introduces some new QuickTime features, new Component
Manager features, and better reliability than other QuickTime versions.
Topics - QuickTime 1.6.1 features, Component Manager 3.0 features and
QuickTime 1.6.1 bug fixes.

 Name  =  QT Overview Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:QT Overview Q&As.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 QT Overview Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  QT for Windows Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:QT for Windows Q&As.sit
 Size:  7K         Date: 6/22/93         Version:
 Description:
 QT for Windows Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  QuickDraw’s Internal Pict D.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:QuickDraw’s Internal Pict D.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 QuickDraw’s Internal Pict D - This technical note describes the internal
format of the QuickDraw picture data structure. This revision corrects some
errors in the opcode descriptions and provides some examples.

 Name  =  QuickTime 1.6 Feat.sit
 Path =  AMUG CD2:Files II:MacTechNotes:QuickTime:QuickTime 1.6 Feat.sit
 Size: 25K         Date: 8/26/93         Version:
 Description:
 QuickTime 1.6 Feat - This Note is a technical discussion of the changes
between QuickTime 1.5 and QuickTime 1.6. QuickTime 1.6 introduces some new
features and is more reliable than other QuickTime versions. The note also
discusses the new features of the QuickTime 1.6 Component Manager. Topics -
QuickTime 1.6 features, Component Manager 3.0 features, QuickTime 1.6 bug
fixes.

 Name  =  ROM Debugger.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:ROM Debugger.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 ROM Debugger - The debugger in ROM (not present on the Macintosh 128,
Macintosh 512, or Macintosh XL) recognizes ROM commands in this document.

 Name  =  RTMP Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:RTMP Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 RTMP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  RegisterName.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:RegisterName.sit
 Size:  4K         Date: 6/22/93         Version:
 Description:
 RegisterName - The verify flag indicator byte (verifyFlag) of the AppleTalk
RegisterName function should always be set TRUE in published code.

 Name  =  ResEdit Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:ResEdit Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 ResEdit Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Reserved Resource Types.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Reserved Resource Types.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Reserved Resource Types - Your applications and desk accessories can create
their own resource types. To avoid using type names which have been or will
be used in the system, Apple has reserved all resource type names which
consist entirely of spaces ($20), lower-case letters ($61 through $7A), and
“international” characters (greater than $7F).

 Name  =  Resolving Alias Files Quiet.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Resolving Alias Files Quiet.sit
 Size: 11K         Date: 6/22/93         Version:
 Description:
 Resolving Alias Files Quiet - ResolveAliasFile always presents the user
identity dialog when mounting remote volumes. This Technical Note offers an
alternative function, ResolveAliasFileMountOption, which uses the
previously undocumented FollowFinderAlias trap to resolve alias files only
if their target is on an already mounted volume. Also included is an
IsAliasFile routine for identifying alias files.

 Name  =  Resource Header App Bytes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Resource Header App Bytes.sit
 Size:  4K         Date: 6/22/93         Version:
 Description:
 Resource Header App Bytes - The section of the Resource Manager chapter of
Inside Macintosh which describes the internal format of a resource file
shows an area of the resource header labeled “available for application
data.” You should not use this area—it is used by the Resource Manager.

 Name  =  Resource Manager Tips.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Resource Manager Tips.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Resource Manager Tips - This note discusses some problems with the Resource
Manager and how to work around them.

 Name  =  Resource Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Resource Mgr Q&As.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Resource Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Resource in CDEV.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Resource in CDEV.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Resource in CDEV - This Technical Note discusses the new 'fwst' resource
added to some Control Panels under System 7.0 and later.

 Name  =  RowBytes Revealed II.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:RowBytes Revealed II.sit
 Size: 10K         Date: 6/22/93         Version:
 Description:
 RowBytes Revealed II - This Technical Note discusses the maximum rowBytes
value for a pixMap.

 Name  =  SADE Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:SADE Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 SADE Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  SCSI Bugs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:SCSI Bugs.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 SCSI Bugs - There are a number of problems in the SCSI Manager; this note
lists the ones we know about, along with an explanation of what we’re doing
about them. Changes made for the 2/88 release are made to more accurately
reflect the state of the SCSI Manager. System 4.1 and 4.2 are very similar;
one bug was fixed in System 4.2.

 Name  =  SCSI H/W Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:SCSI H/W Q&As.sit
 Size: 16K         Date:10/29/92         Version:
 Description:
 SCSI H/W Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  SCSI Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:SCSI Mgr Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 SCSI Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  SCSI Termination.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Apple Workgroup Server:SCSI Termination.sit
 Size:  3K         Date:11/10/93         Version:
 Description:
 SCSI Termination - The introduction of the Apple Workgroup Server 95 has
led to questions with regard to the SCSI termination requirements for the
internal Processor Direct Slot Card and the SCSI busses that it supports.
The internal and external SCSI buses on the AWS95 are two separate
electrical buses that are logically treated as one via software. This means
external cabling and termination issues do not affect the internal bus and
vice-versa. Both buses are terminated at the main board. Find out more by
reading this Technical note.

 Name  =  SCSI Termination.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:SCSI Termination.sit
 Size: 15K         Date: 8/26/93         Version:
 Description:
 SCSI Termination - This Technical Note discusses SCSI termination on the
Macintosh, including the new rules of termination that are necessary with
the advent of the high-speed Macintosh IIfx. Changes since May 1992 - Added
a discussion of Macintosh PowerBook and PowerBook Duo termination and
termination for Apple printers.

 Name  =  SICNs in Menus.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:SICNs in Menus.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 SICNs in Menus - This Technical Note describes a new facility of the Menu
Manager which allows you to add reduced icons and small icons to your
menus. Changes since August 1989. Corrected references to SetItemCmd from
SetItmCmd.

 Name  =  SNMP Transports.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:SNMP Transports.sit
 Size: 13K         Date: 6/22/93         Version:
 Description:
 SNMP Transports - This Technical Note explains how to write an SNMP (Simple
Network Management Protocol) Transport. An SNMP Transport is responsible
for communicating between the SNMP Manager and a particular network layer.
Thus, if you were writing a new network stack for the Macintosh and wanted
it to use the SNMP Manager, you would write an SNMP Transport for your
network stack.

 Name  =  Safe cdevs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Safe cdevs.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Safe cdevs - This Technical Note describes a potential problem with Control
Panel devices (cdevs) that contain EditText fields and presents a way to
avoid it.

 Name  =  Scrap Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Scrap Mgr Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Scrap Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Scrapbook File Format.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Scrapbook File Format.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 Scrapbook File Format - This Technical Note discusses the format of the
System 7.1 Scrapbook file format. The format may change in the future so be
warned.

 Name  =  Script Manager 2.0 Date & T.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Script Manager 2.0 Date & T.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Script Manager 2.0 Date - This Technical Note describes known bugs and
features in and solutions to the date and time routines introduced in
Script Manager 2.0.

 Name  =  Script Manager Print Action.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Script Manager Print Action.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 Script Manager Print Action - This technical note describes how Print
Drivers can access the Script Manager Print Action routine to print
unconventional text, such as Japanese or Arabic.

 Name  =  Script Manager’s Pixel2Char.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Script Manager’s Pixel2Char.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 Script Manager’s Pixel2Char - This Technical Note discusses the Pixel2Char
routine provided by the Script Manager. Changes since June 1989. Clarified
information, corrected minor errors, and replaced the illustration.

 Name  =  Script Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Interapplication Comm.:Script Mgr Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Script Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Script Mgr Variables.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Script Mgr Variables.sit
 Size: 14K         Date:10/29/92         Version:
 Description:
 Script Mgr Variables - This Technical Note describes, in detail, the local
and global script variables.

 Name  =  Searching volumes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Searching volumes.sit
 Size: 15K         Date:10/29/92         Version:
 Description:
 Searching volumes - This Technical Note discusses the PBCatSearch function
and tells why it should be used. It also provides simple algorithms for
searching both MFS and HFS volumes and discusses the problems with indexed
search routines. Changes since October 1988. Includes information on
PBCatSearch and notes the problems with indexed search routines. Source
code examples have been added and revised. Thanks to John Norstad at
Northwestern University for pointing out some of the shortcomings of the
indexed search routines. Thanks to the System 7 engineering team for adding
PBCatSearch.

 Name  =  Segment Loader Limitations.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:Segment Loader Limitations.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Segment Loader Limitations - This Technical Note discusses the jump table
limitations of the Segment Loader and suggests some ways to work around
these limitations to minimize the problem.  These limitations are most
evident to developers using MacApp and other object-oriented environments.

 Name  =  Sense Lines.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Sense Lines.sit
 Size: 14K         Date: 5/03/94         Version: May 94
 Description:
 Sense Lines - Ever wonder how to set up an Apple video card or Macintosh
built-in video to support various size monitors? Well, this Technical Note
will tell you everything you need to know about what monitors are supported
and how. Changes since February 1993 - Updated list to include latest
Macintosh Products as of April 1994. Added discussion of the new type 6
extended sense code. This new code is in addition to the previously
discussed extended sense code protocol which is now designated as type 7.
Show the new type 6 sense codes for three multiple scan monitor
configurations.

 Name  =  Separate Resource Files.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Separate Resource Files.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Separate Resource Files - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Sept 93 Late-Breaking Q&A.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Sept 93 Late-Breaking Q&A.sit
 Size: 21K         Date:11/10/93         Version:
 Description:
 Sept 93 Late-Breaking Q&A - September 1993 Late-Breaking Q&As. This is a
new way of getting special Q&As to you before they’ve been completely
reviewed, copy-edited, and added to the Q&A Tech Notes. The content is
preliminary; it’s been verified by each author, but you might notice
changes when you see the final version in a Q&A Tech Note. Examples of the
questions - What do I have to do to make my CD-ROM driver work with Foreign
File Access? Is Foreign File Access licensable from Apple? My SCSI driver
sometimes hangs and I have to reset the bus. Am I making a common mistake?
What’s the Macintosh built-in analog sound input port signal specification?
Includes many more questions.

 Name  =  Serial Driver Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Serial Driver Q&As.sit
 Size: 13K         Date:10/29/92         Version:
 Description:
 Serial Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Serial GPi The Reliable Way.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Serial GPi The Reliable Way.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Serial GPi The Reliable Way - This Technical Note discusses the latest
supported methods for reading, validating, and configuring the GPi serial
input across all members of the Macintosh family. GPi is a software
configurable serial input present on some machines. It is located at pin 7
on the DIN-8 serial connectors, and connects to the DCD input of the Z8530
Serial Communications Controller (SCC). Because DCD is monopolized by the
mouse on the Macintosh Plus, GPi is not implemented on that machine. Other
machines which do not support GPi include the Macintosh Classic and Mac LC.
On these machines, pins 7 of the DIN-8 serial connectors are not connected.

 Name  =  Serial I/O Port  Q&A.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Serial I/O Port  Q&A.sit
 Size: 10K         Date: 4/12/93         Version:
 Description:
 Serial I/O Port  Q&A - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Serial PollProc.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Serial PollProc.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 Serial PollProc - This Technical Note discusses how to make a PollProc for
your MIDI (Musical Instrument Digital Interface) driver on the Macintosh
PowerBook 140 and 170.

 Name  =  Servers on AppleTalk.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Servers on AppleTalk.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Servers on AppleTalk - Many applications could benefit from the ability to
share common data between several Macintoshes, without requiring a file
server. This technical note discusses one technique for managing this
AppleTalk communication.

 Name  =  SetLineWidth Revealed.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:SetLineWidth Revealed.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 SetLineWidth Revealed - This technical note describes the internal
implementation, and correct method of using, the SetLineWidth Picture
Comment. The SetLineWidth picture comment provides a way of accessing
PostScript’s 'setlinewidth' operator. Since the LaserWriter resolution is
roughly four times that of the Macintosh screen, fractional line widths can
be printed. The SetLineWidth PicComment provides a way for applications to
access these fractional line widths through PostScript, without having to
use floating point numbers.

 Name  =  Setting and Restoring A5.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Setting and Restoring A5.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Setting and Restoring A5 - The routines SetupA5 and RestoreA5 do not work
properly when used with some optimizing Pascal and C compilers. Two new
routines, SetCurrentA5 and SetA5, are available in MPW 3.0, and they should
work with any compiler. Changes since December 1988. Removed the sample
code and expanded the explanation of these two routines. The sample code in
M.TB.MultifinderMisc reflects these new A5 routines.

 Name  =  Signals.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Signals.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Signals - Signals are a form of intra-program interrupt which can greatly
aid clean, inexpensive error trapping in stack frame intensive languages. A
program may invoke the Signal procedure and immediately return to the last
invocation of CatchSignal, including the complete stack frame state at that
point.

 Name  =  Sleep Queue Tasks.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Sleep Queue Tasks.sit
 Size: 10K         Date: 6/22/93         Version:
 Description:
 Sleep Queue Tasks - This Technical Note demonstrates how one can write an
application to display a dialog box before a portable Macintosh goes to
sleep.

 Name  =  Slot Interrupt Priority.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Slot Interrupt Priority.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 Slot Interrupt Priority - This Technical Note describes the way interrupt
priorities are scheduled, which corrects the description of slot interrupt
queue priorities in the Device Manager chapter of Inside Macintosh, Volume
V-426.

 Name  =  Slot Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Slot Mgr Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 Slot Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Sony Drives For You.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Devices:Sony Drives For You.sit
 Size: 19K         Date:10/29/92         Version:
 Description:
 Sony Drives For You - This Technical Note discusses the Sony driver control
and status calls that are available on the Macintosh. Changes since April
1990, Corrected Figure 2, since the Return Physical Drive Icon (csCode =
21) returns an error message instead of an icon on the Macintosh Plus.

 Name  =  Sound Input Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Sound Input Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Sound Input Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Sound Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Sound Mgr Q&As.sit
 Size: 19K         Date:10/29/92         Version:
 Description:
 Sound Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  SourceRoutes.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:SourceRoutes.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 SourceRoutes - This Technical Note discusses source routing and its
possible implementation in token ring link layers.

 Name  =  Spare A Block.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Spare A Block.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 Spare A Block - This Technical Note discusses a new feature of the System
Software 7.0 Disk Initialization Package—bad block sparing.

 Name  =  Speedy Coprocessor.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Speedy Coprocessor.sit
 Size: 17K         Date:10/29/92         Version:
 Description:
 Speedy Coprocessor - This Technical Note presents an overview of the 68881
and 68882 math coprocessors, and it covers general information about the
chips as well as how using the chips directly can help speed your
math–intensive code.

 Name  =  Spool/Print Shared.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Spool/Print Shared.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Spool/Print Shared - This technical note discusses drawbacks of using the
spool-a-page/ print-a-page method of printing.

 Name  =  Spooler Queries?.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Spooler Queries?.sit
 Size:  4K         Date: 6/22/93         Version:
 Description:
 Spooler Queries? - When the LaserShare spooler is on an AppleTalk network,
it acts like a LaserWriter-type device, which can be chosen and
communicated with much like a real LaserWriter. Some applications, however,
must communicate with a LaserWriter directly, not a spooler. If this is
true for your application, you can check whether you are actually talking
to a real LaserWriter by sending to the LaserWriter the following query.

 Name  =  Stand-Alone Code.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Stand-Alone Code.sit
 Size:113K         Date:10/29/92         Version:
 Description:
 Stand-Alone Code - This Technical Note discusses many of the issues related
to stand-alone code modules.  This Note is by no means a completely
original work, as the author borrows freely from the work of Keith Rollin,
Mark Baumwell, and Jim Friedlander. Changes since October 1989. Completely
rewritten to broaden the discussion of stand-alone code modules and include
a greater scope of examples.  Incorporates Technical Notes #110, MPW.
Writing Stand-Alone Code and #145, Debugger FKEY.

 Name  =  Standard File Customization.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Standard File Customization.sit
 Size: 13K         Date:10/29/92         Version:
 Description:
 Standard File Customization - This note contains an example program that
demonstrates how SFPGetFile can be customized using the dialog hook and
file filter functions. SFPGetFile’s dialog hook function and file filter
function enable you to customize SFPGetFile’s behavior to fit the needs of
your application.

 Name  =  Standard File Pkg Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Standard File Pkg Q&As.sit
 Size: 17K         Date:10/29/92         Version:
 Description:
 Standard File Pkg Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Standard File Tips.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Standard File Tips.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Standard File Tips - SFSaveDisk and CurDirStore. Low-memory location $214
(SFSaveDisk—a word) contains –1* the vRefNum of the volume that SF is
displaying (MFS and HFS). It never contains –1* a WDRefNum. Low-memory
location $398 (CurDirStore—a long word) contains the dirID of the directory
that SF is displaying (HFS only). This information can be particularly
useful at hook time, when the vRefNum field of the reply record has not yet
been filled in.

 Name  =  Start Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:Start Mgr Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Start Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Stationery Pads.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Stationery Pads.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Stationery Pads - With the introduction of AppleShare (Apple’s file server)
there are restrictions on self-modification of application resource files
and the placement of configuration files. This note describes one way to
get around the necessity for configuration files.

 Name  =  _StripAddress.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:_StripAddress.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 _StripAddress - Inside Macintosh, Volume V, The OS Utilities, incorrectly
documents the _StripAddress trap; this Technical Note correctly documents
the trap and gives guidelines for its use. Changes since April 1990. Added
a discussion of why the _StripAddress trap should be used under certain
circumstances when patching traps.

 Name  =  Strip _OpenResFile/_Open.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Strip _OpenResFile/_Open.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Strip _OpenResFile/_Open - This Technical Note discusses a bug in
_OpenResFile and _OpenRFPerm which can cause system crashes and what you
can do to avoid this problem.

 Name  =  Styled Text Edit in 6.0.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Styled Text Edit in 6.0.sit
 Size: 13K         Date:10/29/92         Version:
 Description:
 Styled Text Edit in 6.0 - Some changes were made to TextEdit in System 6.0
to provide more functionality and to make life easier for the programmer
using TextEdit.  This Note documents those changes and enhancements.
Changes since August 1988. Corrected an error in TEDispatchRec in the
figure on page 8.

 Name  =  Sub(Launching) H-L Langu.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Processes:Sub(Launching) H-L Langu.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 Sub(Launching) H-L Langu - This Technical Note discusses the “safest”
method of calling _Launch from a high-level language that supports inline
assembly language with the option of launching or sublaunching another
application.

 Name  =  Subject Index.sit
 Path =  AMUG CD2:Files II:MacTechNotes: Indexes:Subject Index.sit
 Size: 34K         Date:10/29/92         Version:
 Description:
 Subject Index - This index expounds upon each of the topics covered in
Technical Notes.

 Name  =  Swapping MMU Mode.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:Swapping MMU Mode.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Swapping MMU Mode - This Technical Note describes how to avoid crashing
when swapping into 32-bit mode on a Macintosh II.  Thanks to Jim Berry and
Dan Weston for pointing this out. Changes since April 1989. Added a
reference to Technical Note #213, _StripAddress:  The Untold Story.

 Name  =  Sys Error Hndlr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:Sys Error Hndlr Q&As.sit
 Size:  6K         Date: 2/23/93         Version:
 Description:
 Sys Error Hndlr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  System Error 33.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:System Error 33.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 System Error 33 - System 3.2 introduced a new system error, ID=33,
generated by the Memory Manager when it notices that a heap had been
corrupted in a certain way. This error is listed in the file “SysErr.a” as
“negZcbFreeErr”.

 Name  =  System S/W Util Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:System S/W Util Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 System S/W Util Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  System Update 2.0.1.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Operating System:System Update 2.0.1.sit
 Size: 10K         Date: 5/03/94         Version: 2.01 tn
 Description:
 System Update 2.0.1 - OS 05 - This Technical Note documents the Macintosh
System Update 2.0.1. System Update 2.0.1 is a collection of bug fixes and
enhancements to Macintosh System 7.1 and System 7 Pro. There have been two
previous versions of this update, called “Macintosh Hardware System Update
Version 1.0,” and “Macintosh Hardware System Update Version 2.0.” Last
updated, October 93.

 Name  =  TEScroll Bug.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TEScroll Bug.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 TEScroll Bug - A bug in TextEdit causes the following problem: a call to
TEScroll with no horizontal or vertical displacement (that is, both dh and
dv set to zero) results in disappearance of the insertion point.

 Name  =  Tags.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Tags.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 Tags - Apple has decided to eliminate support for file-system tags on its
future products; this technical note explains this decision. Some of
Apple’s disk products (and some third-party products) have the ability to
store 532 bytes per sector, instead of the normal 512. Twelve of the extra
bytes are used to store redundant file system information, known as “tags”,
to be used by a scavenging utility to reconstruct damaged disks.

 Name  =  TextEdit Advice & Descent.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TextEdit Advice & Descent.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 TextEdit Advice & Descent - This technical note will point out some bugs
(and possible workarounds), and other items of interest for the TextEdit
programmer.

 Name  =  TextEdit Bugs in 4.2.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TextEdit Bugs in 4.2.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 TextEdit Bugs in 4.2 - This note formerly described the known bugs with the
version of Styled TextEdit that was provided with System 4.1. Many of these
bugs were fixed in System 4.2. This updated Technical Note describes the
remaining known problems.

 Name  =  TextEdit Conversion.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TextEdit Conversion.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 TextEdit Conversion - Text sometimes must be converted between a Pascal
string and “pure” text in a handle. This note illustrates a way to do this
using MPW Pascal.

 Name  =  TextEdit EOL Ambiguity.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TextEdit EOL Ambiguity.sit
 Size:  4K         Date:10/29/92         Version:
 Description:
 TextEdit EOL Ambiguity - TESetSelect may be used to position the insertion
point at the end of a line. There is an ambiguity, though; should the
insertion point appear at the end of the preceding line or the start of the
following one? It is possible to determine what will happen, as you are
about to see.

 Name  =  TextEdit Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TextEdit Q&As.sit
 Size: 12K         Date:10/29/92         Version:
 Description:
 TextEdit Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  TextEdit Record Size Limits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TextEdit Record Size Limits.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 TextEdit Record Size Limits - This Technical Note describes another limit
on the length of a TextEdit record that was previously undocumented.

 Name  =  TextEdit Technicalities.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TextEdit Technicalities.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 TextEdit Technicalities - This Technical Note discusses some areas in
TextEdit that have not previously been clearly documented. Changes since
February 1990. Added a note about the changes in TextEdit for System
Software 6.0.5, documented the low-memory global TESysJust, clarified
information about text direction and _TESetJust, discussed problems with
the SetWordBreak routine along with a solution to work around it, and
described the differences in dialog text item behavior.

 Name  =  Text Services Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:Text Services Mgr Q&As.sit
 Size:  5K         Date: 6/22/93         Version:
 Description:
 Text Services Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  The Compleat Guide to Teach.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:The Compleat Guide to Teach.sit
 Size: 15K         Date: 6/22/93         Version:
 Description:
 The Compleat Guide to Teach - This Technical Note explains how to use
TeachText to create release notes, complete with pictures, which every
Macintosh owner can read. This Note assumes familiarity with ResEdit.

 Name  =  The PAP Status Buffer.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:The PAP Status Buffer.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 The PAP Status Buffer - This Technical Note shows the format of the ATP
data part of Printer Access Protocol (PAP) OpenConnReply and Status
AppleTalk response packets. A PAP client returns this information in its
implementation of the PAPStatus and PAPOpen calls. The status buffer format
is shown for both LaserWriter and ImageWriter (with the ImageWriter II/LQ
LocalTalk Option card installed) printers.

 Name  =  Time Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Processes:Time Mgr Q&As.sit
 Size:  5K         Date:12/28/92         Version:
 Description:
 Time Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Time Space and CopyBits.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Graphics:Time Space and CopyBits.sit
 Size: 21K         Date:10/29/92         Version:
 Description:
 Time Space and CopyBits - This Technical Note describes the various factors
that can influence the speed of _CopyBits so that developers can set up
conditions to achieve the best performance for the particular situation.

 Name  =  Title Index.sit
 Path =  AMUG CD2:Files II:MacTechNotes: Indexes:Title Index.sit
 Size: 11K         Date:10/29/92         Version:
 Description:
 Title Index - This index lists each Tech Note by Title, and gives the
corresponding designation.

 Name  =  Token Ring Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:Token Ring Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Token Ring Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  TokenTlk Programmer's Guide.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:TokenTlk Programmer's Guide.sit
 Size:  9K         Date: 6/22/93         Version:
 Description:
 TokenTlk Programmer's Guide - This Technical Note presents the additions
and changes to the TokenTalk Programmer’s Guide and the latest information
with regard to software development for the Apple Token Ring NB and Token
Ring 4/16 NB network cards.

 Name  =  Toolbox Karma.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Toolbox Karma.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Toolbox Karma - This Technical Note discusses Macintosh Toolbox
compatibility and what you can do to help the Macintosh continue evolving
in the future.

 Name  =  TrueType Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:TrueType Q&As.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 TrueType Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  User Items in Dialogs.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:User Items in Dialogs.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 User Items in Dialogs - The Dialog Manager does not go into detail about
how to manage user items in dialogs; this Technical Note describes the
process. Changes since March 1, 1988. Added MPW C 3.0 code, added a
_SetPort call to the Pascal example, and noted the necessity and meaning of
enabled items.

 Name  =  Using Laser Prep Routines.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Imaging:Printing:Using Laser Prep Routines.sit
 Size:  6K         Date: 6/22/93         Version:
 Description:
 Using Laser Prep Routines - This technical note addresses the issues
involved in depending on the procedures and constants defined in the Laser
Prep dictionary.

 Name  =  Using MPW for Non-Mac 68000.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Using MPW for Non-Mac 68000.sit
 Size: 11K         Date: 6/22/93         Version:
 Description:
 Using MPW for Non-Mac 68000 - This Technical Note discusses using MPW 3.0
for creating software intended to run on 68000-based systems that do not
implement the Macintosh run-time architecture. These systems include NuBus™
cards, peripheral devices, and proprietary 68000 systems.

 Name  =  VCBs and Drive Numbers.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:VCBs and Drive Numbers.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 VCBs and Drive Numbers - The top of page IV-178 in The File Manager chapter
of Inside Macintosh in attempts to explain the behavior of two fields in a
volume control block when the corresponding disk is offline or ejected. Due
to the fact that a little bit is left unsaid, this paragraph is rather
misleading. The two fields in question are vcbDrvNum and vcbDRefNum
(referred to as ioVDrvInfo and ioVDRefNum in C and Pascal). PBHGetVInfo can
be used to access these fields.

 Name  =  VIA Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:VIA Q&As.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 VIA Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  VM and Memory Mappings.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:VM and Memory Mappings.sit
 Size: 20K         Date: 6/22/93         Version:
 Description:
 VM and Memory Mappings - The purpose of this Note is twofold.  First, it
describes in detail how to use the GetPhysical routine.  This routine is
critical to the support of alternate bus masters on certain machines
without Virtual Memory (VM) and all machines with VM.  Included is an
ancillary discussion of several closely-related VM routines.  Second, it
reiterates a number of issues important to VM compatibility and elucidates
some of the deeper VM issues of which specialized developers should be
aware.  Compatibility issues are especially important for developers of
SCSI drivers, NuBus™ master hardware, and code which runs at interrupt
time.

 Name  =  Version Territory.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Version Territory.sit
 Size: 11K         Date:10/29/92         Version:
 Description:
 Version Territory - This Technical Note describes the 'vers' resource
supported by Finder 6.1 and later. Changes since April 1989. Changed MPW C
code to reflect the changes in MPW C 3.1.

 Name  =  Video Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Hardware:Video Q&As.sit
 Size: 18K         Date:10/29/92         Version:
 Description:
 Video Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Virtual Memory Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Memory:Virtual Memory Q&As.sit
 Size:  7K         Date:10/29/92         Version:
 Description:
 Virtual Memory Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Virtual User Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Platforms & Tools:Virtual User Q&As.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Virtual User Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Volume Handling Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Volume Handling Q&As.sit
 Size: 18K         Date:10/29/92         Version:
 Description:
 Volume Handling Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  WDs & MultiFinder.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:WDs & MultiFinder.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 WDs & MultiFinder - This technical note describes the way that working
directories are handled under MultiFinder. Some versions of Technical Note
#77 claim that you can open working directories with a unique ioWDProcID
and that they will only be deallocated when “the system is rebooted.”

 Name  =  WMgrPort.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:WMgrPort.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 WMgrPort - Where WMgrPort (the Window Manager’s port), MultiFinder, and
drawing outside of one’s windows will be reconciled.

 Name  =  WaitNextEvent Bug in 1.0.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:WaitNextEvent Bug in 1.0.sit
 Size:  5K         Date:10/29/92         Version:
 Description:
 WaitNextEvent Bug in 1.0 - This Technical Note discusses a bug in
WaitNextEvent in MultiFinder 1.0. This bug only occurs when WaitNextEvent
is called from the background. This bug will be fixed in the next release
of MultiFinder. Change since 11/87 the bug will be fixed in Systems with
versions greater than $04FF.

 Name  =  Which File System is Active.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Files:Which File System is Active.sit
 Size:  6K         Date:10/29/92         Version:
 Description:
 Which File System is Active - This Technical Note discusses how to
determine which file system a particular volume is running. Changes since
June 1990. Removed text about IDs $0001-$0016 being AppleShare volumes;
other file systems use this range too. Under certain circumstances it is
necessary to determine which file system is currently running on a
particular volume.  For example, on a 64K ROM machine, your application
(i.e., especially disk recovery utilities or disk editors, etc.) may need
to check for MFS versus HFS.  Note that this is usually not necessary,
because all ROMs, except the original 64K ROMs, include HFS.

 Name  =  Window Mgr Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:Window Mgr Q&As.sit
 Size: 12K         Date: 2/28/94         Version:
 Description:
 Window Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.
New Q&As in this Technical Note - How to save and restore window positions.

 Name  =  WordBreak Tables.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:WordBreak Tables.sit
 Size: 10K         Date:10/29/92         Version:
 Description:
 WordBreak Tables - This technical note describes how to construct auxiliary
break tables for use with the FindWord routine in the Script Manager.

 Name  =  WorldScript Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Text:WorldScript Q&As.sit
 Size:  8K         Date: 6/22/93         Version:
 Description:
 WorldScript Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Worldwide Ov Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Overview:Worldwide Ov Q&As.sit
 Size:  9K         Date:12/07/93         Version:
 Description:
 Worldwide Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.
Q&As are now included with Technical Notes to make access to technical
updates easier for you.

 Name  =  X25 & X400 Q&As.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Networking:X25 & X400 Q&As.sit
 Size:  8K         Date:10/29/92         Version:
 Description:
 X25 & X400 Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  ZoomWindow.sit
 Path =  AMUG CD2:Files II:MacTechNotes:Toolbox:ZoomWindow.sit
 Size:  9K         Date:10/29/92         Version:
 Description:
 ZoomWindow - This Technical Note contains some hints about using
_ZoomWindow. Changes since February 1990. Fixed a bug in DoWZoom which
caused crashes if the content of a window did not intersect with any
device’s gdRect.  Also made DoWZoom more robust by making savePort a local
variable and checking for off-screen and inactive GDevice records.  (One
variable name has changed.)  Additional minor changes:  Corrected original
sample code to use _EraseRect before zooming and added references to Human
Interface Note #7, Who’s Zooming Whom? for more subtle and application-
specific considerations.